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

chore(deps): update dependency gatsby to v5.9.1 [security] #18

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) 5.2.0 -> 5.9.1 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 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.


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 gatsby@5.7.0 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 gatsby@5.6.0 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 gatsby@5.4.0 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

v5.3.2

Compare Source

v5.3.1

Compare Source

v5.3.0: v5.3.0

Compare Source

Welcome to gatsby@5.3.0 release (December 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


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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 4210de1 to 6b0e0f8 Compare June 18, 2023 08:25
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 6b0e0f8 to f05be35 Compare June 29, 2023 09:30
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 2781450 to 3584efd Compare July 9, 2023 11:28
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from a26a02b to dee8272 Compare July 19, 2023 11:52
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 719e245 to d456f0d Compare August 1, 2023 13:23
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from d456f0d to cb80be6 Compare August 9, 2023 12:37
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from d09d53f to 39895c6 Compare August 27, 2023 11:42
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from a1362da to f47bc84 Compare September 26, 2023 13:19
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from f47bc84 to 6998945 Compare September 28, 2023 14:35
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 5fb8ad3 to 118cbdf Compare October 15, 2023 12:33
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 118cbdf to 97e95f8 Compare October 23, 2023 16:06
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 97e95f8 to bf24a4c Compare November 6, 2023 07:38
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from bf24a4c to 9c77b26 Compare November 16, 2023 12:21
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 9c77b26 to 4c693b2 Compare December 3, 2023 12:36
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 4c693b2 to 30f66d3 Compare January 28, 2024 09:38
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 30f66d3 to dad8ab2 Compare February 4, 2024 10:55
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from dad8ab2 to 6e2ea99 Compare February 25, 2024 09:59
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 6e2ea99 to 45d1e4d Compare March 12, 2024 13:02
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 07443cc to 469b542 Compare March 24, 2024 18:01
@renovate renovate bot changed the title chore(deps): update dependency gatsby to v5.9.1 [security] chore(deps): update dependency gatsby to v5.9.1 [security] - autoclosed Apr 3, 2024
@renovate renovate bot closed this Apr 3, 2024
@renovate renovate bot deleted the renovate/npm-gatsby-vulnerability branch April 3, 2024 13:26
@renovate renovate bot changed the title chore(deps): update dependency gatsby to v5.9.1 [security] - autoclosed chore(deps): update dependency gatsby to v5.9.1 [security] Apr 3, 2024
@renovate renovate bot reopened this Apr 3, 2024
@renovate renovate bot restored the renovate/npm-gatsby-vulnerability branch April 3, 2024 15:43
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 469b542 to 7ed3e36 Compare April 3, 2024 15:49
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 7ed3e36 to 12a30ec Compare April 14, 2024 09:52
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from e322b69 to 9330860 Compare April 25, 2024 09:48
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 9330860 to 6f64e65 Compare June 4, 2024 13:16
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 6f64e65 to 86a7ec8 Compare July 21, 2024 14:34
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 86a7ec8 to 1385867 Compare August 6, 2024 08:14
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 1385867 to a81759c Compare August 28, 2024 07:25
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from a81759c to d771f3c Compare October 9, 2024 09:50
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from d771f3c to fc8007a Compare December 2, 2024 12:22
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