-
Notifications
You must be signed in to change notification settings - Fork 14
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
fix(deps): update dependency next to v14 [security] #1342
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/npm-next-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.
+14
−156
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 8, 2024 21:22
37e3334
to
6b93aa5
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 9, 2024 01:33
6b93aa5
to
3739af9
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 9, 2024 01:37
3739af9
to
c23bdf4
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 9, 2024 04:07
c23bdf4
to
cf6e4b8
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 15, 2024 20:57
cf6e4b8
to
633ff91
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 15, 2024 23:12
633ff91
to
f94dd2d
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 17, 2024 00:40
f94dd2d
to
4c21c94
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 23, 2024 01:58
4c21c94
to
71c8126
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 24, 2024 14:07
71c8126
to
766b4ca
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
November 6, 2024 01:18
7198e11
to
95fe9af
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
November 13, 2024 22:42
95fe9af
to
fb01b0e
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
November 22, 2024 19:53
fb01b0e
to
ce9131d
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
November 22, 2024 20:00
ce9131d
to
c6da1a3
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
November 22, 2024 20:06
c6da1a3
to
d0e335f
Compare
renovate
bot
changed the title
fix(deps): update dependency next to v14 [security]
fix(deps): update dependency next to v14 [security] - autoclosed
Dec 8, 2024
renovate
bot
changed the title
fix(deps): update dependency next to v14 [security] - autoclosed
fix(deps): update dependency next to v14 [security]
Dec 8, 2024
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
2 times, most recently
from
December 9, 2024 02:03
d0e335f
to
af8cc71
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 9, 2024 09:07
af8cc71
to
cf382d8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^13.0.7
->^14.0.0
GitHub Vulnerability Alerts
CVE-2024-34351
Impact
A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions by security researchers at Assetnote. If the
Host
header is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself.Prerequisites
<14.1.1
) is running in a self-hosted* manner./
.* Many hosting providers (including Vercel) route requests based on the Host header, so we do not believe that this vulnerability affects any Next.js applications where routing is done in this manner.
Patches
This vulnerability was patched in #62561 and fixed in Next.js
14.1.1
.Workarounds
There are no official workarounds for this vulnerability. We recommend upgrading to Next.js
14.1.1
.Credit
Vercel and the Next.js team thank Assetnote for responsibly disclosing this issue to us, and for working with us to verify the fix. Thanks to:
Adam Kues - Assetnote
Shubham Shah - Assetnote
CVE-2024-47831
Impact
The image optimization feature of Next.js contained a vulnerability which allowed for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption.
Not affected:
next.config.js
file is configured withimages.unoptimized
set totrue
orimages.loader
set to a non-default value.Patches
This issue was fully patched in Next.js
14.2.7
. We recommend that users upgrade to at least this version.Workarounds
Ensure that the
next.config.js
file has eitherimages.unoptimized
,images.loader
orimages.loaderFile
assigned.Credits
Brandon Dahler (brandondahler), AWS
Dimitrios Vlastaras
CVE-2024-51479
Impact
If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application's root directory. For example:
https://example.com/
https://example.com/foo
https://example.com/foo/bar
Patches
This issue was patched in Next.js
14.2.15
and later.If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version.
Workarounds
There are no official workarounds for this vulnerability.
Credits
We'd like to thank tyage (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.
Release Notes
vercel/next.js (next)
v14.2.7
Compare Source
v14.2.6
Compare Source
v14.2.5
Compare Source
v14.2.4
Compare Source
Core Changes
Credits
Huge thanks to @ztanner, @ijjk, @wbinnssmith, @huozhi, and @lubieowoce for helping!
v14.2.3
Compare Source
v14.2.2
Compare Source
v14.2.1
Compare Source
v14.2.0
Compare Source
v14.1.4
Compare Source
v14.1.3
Compare Source
v14.1.2
Compare Source
v14.1.1
Compare Source
Note: this is a backport release for critical bug fixes -- this does not include all pending features/changes on canary
Core Changes
Credits
Huge thanks to @huozhi, @shuding, @Ethan-Arrowood, @styfle, @ijjk, @ztanner, @balazsorban44, @kdy1, and @williamli for helping!
v14.1.0
Compare Source
v14.0.4
Compare Source
v14.0.3
Compare Source
v14.0.2
Compare Source
v14.0.1
Compare Source
Core Changes
8c8ee9e
to0c63487
and types: #57772Documentation Changes
Example Changes
with-youtube-embed
example: #57367with-google-maps-embed
example: #57365Misc Changes
create-next-app
: #57262Credits
Huge thanks to @dijonmusters, @sokra, @philwolstenholme, @IgorKowalczyk, @housseindjirdeh, @Zoe-Bot, @HanCiHu, @JackHowa, @goncy, @hirotomoyamada, @pveyes, @yeskunall, @vinaykulk621, @ChendayUP, @leerob, @dvoytenko, @mknichel, @ijjk, @hmaesta, @ajz003, @its-kunal, @joelhooks, @blurrah, @tariknh, @Vinlock, @Nayeem-XTREME, @aziyatali, @aspehler, @huozhi, @ztanner, @ForsakenHarmony, @moka-ayumu, and @gnoff for helping!
v14.0.0
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 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.