-
Notifications
You must be signed in to change notification settings - Fork 1
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
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/npm-gatsby-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
2 times, most recently
from
June 18, 2023 08:25
4210de1
to
6b0e0f8
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
June 29, 2023 09:30
6b0e0f8
to
f05be35
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
2 times, most recently
from
July 9, 2023 11:28
2781450
to
3584efd
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
2 times, most recently
from
July 19, 2023 11:52
a26a02b
to
dee8272
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
2 times, most recently
from
August 1, 2023 13:23
719e245
to
d456f0d
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
August 9, 2023 12:37
d456f0d
to
cb80be6
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
2 times, most recently
from
August 27, 2023 11:42
d09d53f
to
39895c6
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
2 times, most recently
from
September 26, 2023 13:19
a1362da
to
f47bc84
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
September 28, 2023 14:35
f47bc84
to
6998945
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
2 times, most recently
from
October 15, 2023 12:33
5fb8ad3
to
118cbdf
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
October 23, 2023 16:06
118cbdf
to
97e95f8
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
November 6, 2023 07:38
97e95f8
to
bf24a4c
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
November 16, 2023 12:21
bf24a4c
to
9c77b26
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
December 3, 2023 12:36
9c77b26
to
4c693b2
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
January 28, 2024 09:38
4c693b2
to
30f66d3
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
February 4, 2024 10:55
30f66d3
to
dad8ab2
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
February 25, 2024 09:59
dad8ab2
to
6e2ea99
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
March 12, 2024 13:02
6e2ea99
to
45d1e4d
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
2 times, most recently
from
March 24, 2024 18:01
07443cc
to
469b542
Compare
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
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
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
April 3, 2024 15:49
469b542
to
7ed3e36
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
April 14, 2024 09:52
7ed3e36
to
12a30ec
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
2 times, most recently
from
April 25, 2024 09:48
e322b69
to
9330860
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
June 4, 2024 13:16
9330860
to
6f64e65
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
July 21, 2024 14:34
6f64e65
to
86a7ec8
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
August 6, 2024 08:14
86a7ec8
to
1385867
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
August 28, 2024 07:25
1385867
to
a81759c
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
October 9, 2024 09:50
a81759c
to
d771f3c
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
December 2, 2024 12:22
d771f3c
to
fc8007a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.2.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
Compare Source
v5.9.0
Compare Source
v5.8.1
Compare Source
v5.8.0
Compare Source
v5.7.0
: v5.7.0Compare 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.0Compare Source
Welcome to
gatsby@5.6.0
release (February 2023 #1)Key highlights of this release:
wrapRootElement
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.0Compare 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.0Compare 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.
This PR was generated by Mend Renovate. View the repository job log.