Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency gatsby [security] #618

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 14, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
gatsby (source, changelog) 5.3.2 -> 5.9.1 age adoption passing confidence
gatsby (source, changelog) 4.25.0 -> 4.25.7 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2023-34238

Impact

The Gatsby framework prior to versions 4.25.7 and 5.9.1 contain a Local File Inclusion vulnerability in the __file-code-frame and __original-stack-frame paths, exposed when running the Gatsby develop server (gatsby develop).

The following steps can be used to reproduce the vulnerability:


# Create a new Gatsby project
$ npm init gatsby
$ cd my-gatsby-site

# Start the Gatsby develop server
$ gatsby develop

# Execute the Local File Inclusion vulnerability in __file-code-frame
$ curl "http://127.0.0.1:8000/__file-code-frame?filePath=/etc/passwd&lineNumber=1"

# Execute the Local File Inclusion vulnerability in __original-stack-frame
$ curl "http://127.0.0.1:8000/__original-stack-frame?moduleId=/etc/hosts&lineNumber=1&skipSourceMap=1"

It should be noted that by default gatsby develop is only accessible via the localhost 127.0.0.1, and one would need to intentionally expose the server to other interfaces to exploit this vulnerability by using server options such as --host 0.0.0.0, -H 0.0.0.0, or the GATSBY_HOST=0.0.0.0 environment variable.

Patches

A patch has been introduced in [email protected] and [email protected] which mitigates the issue.

Workarounds

As stated above, by default gatsby develop is only exposed to the localhost 127.0.0.1. For those using the develop server in the default configuration no risk is posed. If other ranges are required, preventing the develop server from being exposed to untrusted interfaces or IP address ranges would mitigate the risk from this vulnerability.

We encourage projects to upgrade to the latest major release branch for all Gatsby plugins to ensure the latest security updates and bug fixes are received in a timely manner.

Credits

We would like to thank Maxwell Garrett of Assetnote for bringing the __file-code-frame issue to our attention.

For more information

Email us at [email protected].


Release Notes

gatsbyjs/gatsby (gatsby)

v5.9.1

Compare Source

v5.9.0

Compare Source

v5.8.1

Compare Source

v5.8.0

Compare Source

v5.7.0: v5.7.0

Compare Source

Welcome to [email protected] release (February 2023 #2)

This release focused on bug fixes and perf improvements. Check out notable bugfixes and improvements.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.6.1

Compare Source

v5.6.0: v5.6.0

Compare Source

Welcome to [email protected] release (February 2023 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.5.0

Compare Source

v5.4.2

Compare Source

v5.4.1

Compare Source

v5.4.0: v5.4.0

Compare Source

Welcome to [email protected] release (January 2023 #1)

The whole team took time off for a much deserved winter break and we hope you had relaxing holidays, too! Before the break we spent time doing maintenance work such as updating internal dependencies or fixing some smaller bugs here and there. In case you missed it, we shipped ES Modules (ESM) in Gatsby files in the last release.

So check out the notable bugfixes section to learn more.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.3.3

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner June 14, 2023 12:22
@netlify
Copy link

netlify bot commented Jun 14, 2023

Deploy Preview for netlify-plugin-gatsby-demo-v5 ready!

Name Link
🔨 Latest commit 06ac4fd
🔍 Latest deploy log https://app.netlify.com/sites/netlify-plugin-gatsby-demo-v5/deploys/661fde634c1273000805a77c
😎 Deploy Preview https://deploy-preview-618--netlify-plugin-gatsby-demo-v5.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@netlify
Copy link

netlify bot commented Jun 14, 2023

Deploy Preview for netlify-plugin-gatsby-demo ready!

Name Link
🔨 Latest commit 06ac4fd
🔍 Latest deploy log https://app.netlify.com/sites/netlify-plugin-gatsby-demo/deploys/661fde631cd5c100085287b1
😎 Deploy Preview https://deploy-preview-618--netlify-plugin-gatsby-demo.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from e2ccca6 to 21f72be Compare June 14, 2023 12:54
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 21f72be to 58ed8d3 Compare June 23, 2023 14:44
@nickytonline nickytonline enabled auto-merge (squash) June 23, 2023 20:32
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 3 times, most recently from 435d369 to be2a0f4 Compare June 29, 2023 12:42
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from be2a0f4 to 36cecf2 Compare July 5, 2023 13:05
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 36cecf2 to f6af072 Compare July 26, 2023 13:27
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from f6af072 to 97dfccf Compare August 7, 2023 14:30
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 97dfccf to 72690da Compare October 9, 2023 13:06
@kodiakhq kodiakhq bot removed the automerge label Oct 9, 2023
@kodiakhq
Copy link
Contributor

kodiakhq bot commented Oct 9, 2023

This PR currently has a merge conflict. Please resolve this and then re-add the automerge label.

@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from c3eb261 to cfc1c55 Compare October 11, 2023 22:46
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 569d73c to 76f4ac2 Compare February 26, 2024 00:45
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 76f4ac2 to 06ac4fd Compare April 17, 2024 14:36
@renovate renovate bot changed the title chore(deps): update dependency gatsby [security] fix(deps): update dependency gatsby [security] Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant