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

Update dependency gatsby to v4.25.7 [SECURITY] #85

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 10, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
gatsby (source, changelog) 4.24.8 -> 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)

v4.25.7

Compare Source

v4.25.6

Compare Source

v4.25.5

Compare Source

v4.25.4

Compare Source

v4.25.3

Compare Source

v4.25.2

Compare Source

v4.25.1

Compare Source

v4.25.0

Compare Source


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 changed the title Update dependency gatsby to v4.25.7 [SECURITY] Update dependency gatsby to v4.25.7 [SECURITY] - autoclosed Oct 25, 2023
@renovate renovate bot closed this Oct 25, 2023
@renovate renovate bot deleted the renovate/npm-gatsby-vulnerability branch October 25, 2023 20:10
@renovate renovate bot changed the title Update dependency gatsby to v4.25.7 [SECURITY] - autoclosed Update dependency gatsby to v4.25.7 [SECURITY] Oct 25, 2023
@renovate renovate bot reopened this Oct 25, 2023
@renovate renovate bot restored the renovate/npm-gatsby-vulnerability branch October 25, 2023 21:20
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 8bcfe5a to 1e968d9 Compare October 25, 2023 21:20
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.

0 participants