-
Notifications
You must be signed in to change notification settings - Fork 22
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.2.15 [security] #6375
Open
renovate
wants to merge
1
commit into
dev
Choose a base branch
from
renovate/npm-next-vulnerability
base: dev
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-next-vulnerability
branch
from
December 18, 2024 09:55
6201f9f
to
f72b076
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 18, 2024 11:15
f72b076
to
f108c3f
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 18, 2024 11:34
f108c3f
to
adf8127
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 18, 2024 14:09
adf8127
to
e415219
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 19, 2024 08:51
e415219
to
1f1fda6
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 19, 2024 14:28
1f1fda6
to
eb2e0fa
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 19, 2024 15:13
eb2e0fa
to
ecad41c
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 19, 2024 15:17
ecad41c
to
af178dd
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 19, 2024 15:27
af178dd
to
8b74efe
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 19, 2024 15:49
8b74efe
to
77485d7
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 19, 2024 16:06
77485d7
to
49f47d9
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 20, 2024 10:00
49f47d9
to
418a99a
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:
14.2.11
->14.2.15
GitHub Vulnerability Alerts
CVE-2023-46298
Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be cached by a CDN, causing a denial of service to all users requesting the same URL via that CDN. Cloudflare considers these requests cacheable assets.
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.
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.15
Compare Source
Core Changes
Credits
Huge thanks to @ztanner, @agadzik, @huozhi, @styfle, @icyJoseph and @wyattjoh for helping!
v14.2.14
Compare Source
Core Changes
Credits
Huge thanks to @styfle, @ztanner, @ijjk, @huozhi and @wyattjoh for helping!
v14.2.13
Compare Source
v14.2.12
Compare Source
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Paris, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.