-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update dependency gatsby to v5.9.1 [SECURITY] #270
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
from
June 13, 2023 14:37
81d5d00
to
5c38a95
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
June 18, 2023 08:06
5c38a95
to
09ec13d
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
June 29, 2023 12:15
09ec13d
to
8bfdb15
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
July 1, 2023 16:26
8bfdb15
to
6b0ebe4
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
July 6, 2023 13:09
6b0ebe4
to
5700e15
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
July 9, 2023 09:44
5700e15
to
c6c71d8
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
July 16, 2023 13:51
c6c71d8
to
9db1085
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
July 19, 2023 09:46
9db1085
to
6c135f1
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
July 27, 2023 16:28
6c135f1
to
d482220
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
August 1, 2023 16:56
d482220
to
688dff1
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
August 9, 2023 15:29
688dff1
to
ac36f95
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
August 13, 2023 07:37
ac36f95
to
18ae21b
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
August 22, 2023 20:41
18ae21b
to
079fe42
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
August 27, 2023 08:20
079fe42
to
b7f8a40
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
September 15, 2023 18:36
b7f8a40
to
aabd828
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
February 25, 2024 10:54
1ce5ade
to
b60db6d
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
March 12, 2024 09:44
b60db6d
to
a1c505d
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
March 20, 2024 16:33
a1c505d
to
c7103ac
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
March 24, 2024 14:59
c7103ac
to
abf599c
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
April 14, 2024 09:35
abf599c
to
98caf54
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
April 21, 2024 10:57
98caf54
to
4226402
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
April 25, 2024 10:26
4226402
to
b544843
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
June 4, 2024 10:10
b544843
to
9d55ae7
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
June 24, 2024 17:02
9d55ae7
to
f2aee6e
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
July 21, 2024 14:30
f2aee6e
to
78ed8b8
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
August 6, 2024 09:46
78ed8b8
to
d1b782a
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
August 28, 2024 09:43
d1b782a
to
f978c71
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
October 9, 2024 11:53
f978c71
to
d940b02
Compare
renovate
bot
force-pushed
the
renovate/npm-gatsby-vulnerability
branch
from
December 2, 2024 10:25
d940b02
to
6944d7e
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.9.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
[email protected]
and[email protected]
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 [email protected].
Release Notes
gatsbyjs/gatsby (gatsby)
v5.9.1
Compare Source
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 is behind base branch, 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.