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 to v4.25.7 [security] #1043

Merged
merged 1 commit into from
Mar 27, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 15, 2023

Mend Renovate

This PR contains the following updates:

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


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.

🔕 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 has been generated by Mend Renovate. View repository job log here.

@ghost
Copy link

ghost commented Jun 15, 2023

👇 Click on the image for a new way to code review

Review these changes using an interactive CodeSee Map

Legend

CodeSee Map legend

@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 0410431 to 12b9057 Compare July 21, 2023 05:18
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 117830c to 988a653 Compare October 8, 2023 19:33
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 988a653 to efe86f3 Compare October 13, 2023 04:53
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 3 times, most recently from d28d341 to 1e602b3 Compare October 24, 2023 15:02
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 1e602b3 to 1d8905e Compare November 18, 2023 02:16
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 1d8905e to 686d2bf Compare November 28, 2023 14:34
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 686d2bf to 0a134b4 Compare December 21, 2023 18:23
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 5 times, most recently from adc9abf to 70855da Compare February 6, 2024 18:34
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 6 times, most recently from ceea052 to eadc1fb Compare February 15, 2024 04:03
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 3 times, most recently from 1073ffb to 1b5a650 Compare February 18, 2024 22:44
@renovate renovate bot enabled auto-merge (rebase) March 27, 2024 22:03
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 1b5a650 to 907418a Compare March 27, 2024 22:03
@renovate renovate bot merged commit aaa3496 into saga Mar 27, 2024
1 of 3 checks passed
@renovate renovate bot deleted the renovate/npm-gatsby-vulnerability branch March 27, 2024 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants