Skip to content

fix(deps): update dependency gatsby to v4.25.7 [security]#310

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-gatsby-vulnerability
Open

fix(deps): update dependency gatsby to v4.25.7 [security]#310
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-gatsby-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jun 10, 2023

This PR contains the following updates:

Package Change Age Confidence
gatsby (source, changelog) 4.21.14.25.7 age confidence

Gatsby develop server has Local File Inclusion vulnerability

CVE-2023-34238 / GHSA-c6f8-8r25-c4gc

More information

Details

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 gatsby@5.9.1 and gatsby@4.25.7 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 security@gatsbyjs.com.

Severity

  • CVSS Score: 4.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


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

v4.24.8

Compare Source

v4.24.7

Compare Source

v4.24.6

Compare Source

v4.24.5

Compare Source

v4.24.4

Compare Source

v4.24.3

Compare Source

v4.24.2

Compare Source

v4.24.1

Compare Source

v4.24.0: v4.24

Compare Source

Welcome to gatsby@4.24.0 release (September 2022 #2)

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

v4.23.1

Compare Source

v4.23.0: v4.23

Compare Source

Welcome to gatsby@4.23.0 release (September 2022 #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

v4.22.1

Compare Source

v4.22.0: v4.22

Compare Source

Welcome to gatsby@4.22.0 release (August 2022 #3)

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


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • 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 these updates again.


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

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

@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 10, 2023

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
giuem-com Error Error Apr 29, 2026 8:32pm

@renovate renovate Bot changed the title chore(deps): update dependency gatsby to v4.25.7 [security] chore(deps): update dependency gatsby to v4.25.7 [security] - autoclosed Sep 21, 2023
@renovate renovate Bot closed this Sep 21, 2023
@renovate renovate Bot deleted the renovate/npm-gatsby-vulnerability branch September 21, 2023 12:24
@renovate renovate Bot changed the title chore(deps): update dependency gatsby to v4.25.7 [security] - autoclosed chore(deps): update dependency gatsby to v4.25.7 [security] Sep 21, 2023
@renovate renovate Bot reopened this Sep 21, 2023
@renovate renovate Bot restored the renovate/npm-gatsby-vulnerability branch September 21, 2023 15:29
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from b72d8d8 to e50048d Compare September 21, 2023 15:30
@renovate renovate Bot changed the title chore(deps): update dependency gatsby to v4.25.7 [security] fix(deps): update dependency gatsby to v4.25.7 [security] Dec 10, 2024
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from e50048d to 32d7574 Compare August 10, 2025 15:09
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from 32d7574 to 586c2b8 Compare August 31, 2025 10:46
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from 586c2b8 to 639c359 Compare September 25, 2025 15:47
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from 639c359 to baf9c2d Compare October 21, 2025 15:06
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from baf9c2d to a41d68a Compare November 10, 2025 15:44
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from a41d68a to 864c4a0 Compare November 18, 2025 10:38
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from 864c4a0 to 68051fc Compare December 31, 2025 16:33
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from 68051fc to 7b6a22e Compare January 23, 2026 18:32
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from 7b6a22e to ba37c2e Compare March 5, 2026 17:30
@renovate renovate Bot changed the title fix(deps): update dependency gatsby to v4.25.7 [security] fix(deps): update dependency gatsby to v4.25.7 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate renovate Bot deleted the renovate/npm-gatsby-vulnerability branch March 27, 2026 01:25
@renovate renovate Bot changed the title fix(deps): update dependency gatsby to v4.25.7 [security] - autoclosed fix(deps): update dependency gatsby to v4.25.7 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from ba37c2e to d869860 Compare March 30, 2026 17:33
@renovate renovate Bot force-pushed the renovate/npm-gatsby-vulnerability branch from d869860 to 15285bd Compare April 29, 2026 20:32
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