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.
gatsbyjs/gatsby (gatsby)
### [`v5.9.1`](https://togithub.com/gatsbyjs/gatsby/compare/e95b10ae0d7c6f01b627217333eb9a630f16e546...774313bf9400c4cc817b5e078388bba55997269a)
[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.9.0...gatsby@5.9.1)
### [`v5.9.0`](https://togithub.com/gatsbyjs/gatsby/compare/12c91db83842327398193676395693b1f9fff6ac...e95b10ae0d7c6f01b627217333eb9a630f16e546)
[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.8.1...gatsby@5.9.0)
### [`v5.8.1`](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.8.0...gatsby@5.8.1)
[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.8.0...gatsby@5.8.1)
### [`v5.8.0`](https://togithub.com/gatsbyjs/gatsby/compare/5d64c3e84b91277f7f86b544b1e2e6447da50770...b1abb5bc91abdf3f966c8920c9c1fd757b8c5831)
[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.7.0...gatsby@5.8.0)
### [`v5.7.0`](https://togithub.com/gatsbyjs/gatsby/releases/tag/gatsby%405.7.0): v5.7.0
[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.6.1...gatsby@5.7.0)
Welcome to `gatsby@5.7.0` release (February 2023 #2)
This release focused on bug fixes and perf improvements. Check out [notable bugfixes and improvements](https://www.gatsbyjs.com/docs/reference/release-notes/v5.7#notable-bugfixes--improvements).
**Bleeding Edge:** Want to try new features as soon as possible? Install `gatsby@next` and let us know if you have any [issues](https://togithub.com/gatsbyjs/gatsby/issues).
[Previous release notes](https://www.gatsbyjs.com/docs/reference/release-notes/v5.6)
[Full changelog](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.7.0-next.0...gatsby@5.7.0)
### [`v5.6.1`](https://togithub.com/gatsbyjs/gatsby/compare/8419b3490e937f76f1264505e9e30032adac9fff...33ed42360bd28a36eaad4c9c9a1a6e2776e1d037)
[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.6.0...gatsby@5.6.1)
### [`v5.6.0`](https://togithub.com/gatsbyjs/gatsby/releases/tag/gatsby%405.6.0): v5.6.0
[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.5.0...gatsby@5.6.0)
Welcome to `gatsby@5.6.0` release (February 2023 #1)
Key highlights of this release:
- [Gatsby is joining Netlify](https://www.gatsbyjs.com/docs/reference/release-notes/v5.6/#gatsby-is-joining-netlify)
- [Head API supports context providers from `wrapRootElement`](https://www.gatsbyjs.com/docs/reference/release-notes/v5.6/#head-api-supports-context-providers-from-wraprootelement)
**Bleeding Edge:** Want to try new features as soon as possible? Install `gatsby@next` and let us know if you have any [issues](https://togithub.com/gatsbyjs/gatsby/issues).
[Previous release notes](https://www.gatsbyjs.com//docs/reference/release-notes/v5.5)
[Full changelog](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.6.0-next.0...gatsby@5.6.0)
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 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 contains the following updates:
5.5.0
->5.9.1
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:
It should be noted that by default
gatsby develop
is only accessible via the localhost127.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 theGATSBY_HOST=0.0.0.0
environment variable.Patches
A patch has been introduced in
gatsby@5.9.1
andgatsby@4.25.7
which mitigates the issue.Workarounds
As stated above, by default
gatsby develop
is only exposed to the localhost127.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.
Release Notes
gatsbyjs/gatsby (gatsby)
### [`v5.9.1`](https://togithub.com/gatsbyjs/gatsby/compare/e95b10ae0d7c6f01b627217333eb9a630f16e546...774313bf9400c4cc817b5e078388bba55997269a) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.9.0...gatsby@5.9.1) ### [`v5.9.0`](https://togithub.com/gatsbyjs/gatsby/compare/12c91db83842327398193676395693b1f9fff6ac...e95b10ae0d7c6f01b627217333eb9a630f16e546) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.8.1...gatsby@5.9.0) ### [`v5.8.1`](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.8.0...gatsby@5.8.1) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.8.0...gatsby@5.8.1) ### [`v5.8.0`](https://togithub.com/gatsbyjs/gatsby/compare/5d64c3e84b91277f7f86b544b1e2e6447da50770...b1abb5bc91abdf3f966c8920c9c1fd757b8c5831) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.7.0...gatsby@5.8.0) ### [`v5.7.0`](https://togithub.com/gatsbyjs/gatsby/releases/tag/gatsby%405.7.0): v5.7.0 [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.6.1...gatsby@5.7.0) Welcome to `gatsby@5.7.0` release (February 2023 #2) This release focused on bug fixes and perf improvements. Check out [notable bugfixes and improvements](https://www.gatsbyjs.com/docs/reference/release-notes/v5.7#notable-bugfixes--improvements). **Bleeding Edge:** Want to try new features as soon as possible? Install `gatsby@next` and let us know if you have any [issues](https://togithub.com/gatsbyjs/gatsby/issues). [Previous release notes](https://www.gatsbyjs.com/docs/reference/release-notes/v5.6) [Full changelog](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.7.0-next.0...gatsby@5.7.0) ### [`v5.6.1`](https://togithub.com/gatsbyjs/gatsby/compare/8419b3490e937f76f1264505e9e30032adac9fff...33ed42360bd28a36eaad4c9c9a1a6e2776e1d037) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.6.0...gatsby@5.6.1) ### [`v5.6.0`](https://togithub.com/gatsbyjs/gatsby/releases/tag/gatsby%405.6.0): v5.6.0 [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.5.0...gatsby@5.6.0) Welcome to `gatsby@5.6.0` release (February 2023 #1) Key highlights of this release: - [Gatsby is joining Netlify](https://www.gatsbyjs.com/docs/reference/release-notes/v5.6/#gatsby-is-joining-netlify) - [Head API supports context providers from `wrapRootElement`](https://www.gatsbyjs.com/docs/reference/release-notes/v5.6/#head-api-supports-context-providers-from-wraprootelement) **Bleeding Edge:** Want to try new features as soon as possible? Install `gatsby@next` and let us know if you have any [issues](https://togithub.com/gatsbyjs/gatsby/issues). [Previous release notes](https://www.gatsbyjs.com//docs/reference/release-notes/v5.5) [Full changelog](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@5.6.0-next.0...gatsby@5.6.0)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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.