-
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
fix(deps): update dependency next to v14 [security] #510
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.
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
May 13, 2024 04:57
d6bae74
to
b5acdd5
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
May 20, 2024 11:31
b5acdd5
to
65a170d
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
May 27, 2024 04:36
65a170d
to
03b5d08
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
June 3, 2024 04:07
03b5d08
to
26922eb
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
June 10, 2024 03:35
26922eb
to
e0dae17
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
June 10, 2024 06:12
e0dae17
to
6286b50
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
June 17, 2024 03:53
6286b50
to
2faa6cc
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
July 6, 2024 00:44
2faa6cc
to
e61ba66
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
July 8, 2024 04:13
e61ba66
to
3f63b68
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
July 15, 2024 03:05
3f63b68
to
b843505
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
July 22, 2024 05:21
b843505
to
b0e0e04
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
August 3, 2024 07:09
b0e0e04
to
e413a92
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
August 5, 2024 03:17
e413a92
to
2ab247a
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
August 12, 2024 04:46
2ab247a
to
2755889
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
August 26, 2024 04:05
2755889
to
373f879
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 2, 2024 04:41
373f879
to
0f6b57f
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 9, 2024 04:13
0f6b57f
to
a71942a
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 16, 2024 04:05
a71942a
to
dc4b9bf
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 23, 2024 03:38
dc4b9bf
to
2ccc4ee
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 30, 2024 03:55
2ccc4ee
to
35d38b7
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 7, 2024 03:39
35d38b7
to
afbc2d4
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 14, 2024 03:33
afbc2d4
to
c06fbf7
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 21, 2024 03:23
c06fbf7
to
1ad6fdb
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 28, 2024 03:44
1ad6fdb
to
02aaded
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
November 4, 2024 04:25
02aaded
to
fdc317f
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:
^13.1.6
->^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
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.