-
Notifications
You must be signed in to change notification settings - Fork 6
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 next to v12.3.5 [SECURITY] #54
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-next-vulnerability
base: master
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 ↗︎
|
b95eaf2
to
2047d38
Compare
49ff474
to
2047d38
Compare
2047d38
to
73b5e96
Compare
73b5e96
to
155d4b5
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:
12.1.0
->12.3.5
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.
CVE-2025-29927
Impact
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
Patches
15.2.3
14.2.25
13.5.9
12.3.5
Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.
Workaround
If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the
x-middleware-subrequest
header from reaching your Next.js application.Credits
Release Notes
vercel/next.js (next)
v12.3.5
Compare Source
v12.3.4
Compare Source
v12.3.3
Compare Source
v12.3.2
Compare Source
v12.3.1
Compare Source
Core Changes
experimental: { esmExternals: 'loose' }
: #40377next/dynamic
should only add default loading without suspense: #40397AppType
: #40391onLoad
concurrent rendering resilient: #40191fallbackNodePolyfills: false
: #40612notFound: true
in/
withnext export
: #40592CONTRIBUTING.md
: #40515Documentation Changes
swcMinify: true
out of "Experimental features" section: #40394loading
property: #40488Example Changes
Misc Changes
link:
instead offile:
in CONTRIBUTING.md: #40510/errors/
directory.tar
: #40513next/script
beforeInteractive test in both dev & prod: #40541Credits
Huge thanks to @huozhi, @shuding, @ijjk, @jasham, @Kikobeats, @wyattjoh, @rubytree33, @timneutkens, @balazsorban44, @andrewrjohn, @SukkaW, @hanneslund, @leerob, @Djo1e, @kdy1, @msafi, @tknickman, @feugy, @cramforce, @ryparker, @victorboucher, @steven-tey, @JDansercoer, @janklimo, @hiro0218, @HaNdTriX, @migueloller, @flex-kyunghwa, @saalimzafar, @alxhotel, @janicklas-ralph, @feedthejim, and @chornos13 for helping!
v12.3.0
Compare Source
Core Changes
SPACE_AROUND_COLON
regex: #39710fetch
response: #39608onError
handling innext/future/image
: #39824next/future/image
whenobjectFit
orobjectPosition
: #39614next/future/image
blur-up placeholder : #39785@vercel/nft@0.22.0
: #39906AppProps
's generic forpageProps
: #38867next/future/image
incorrectly warning forfill
+blur
: #39986experimental.fallbackNodePolyfills
flag: #39248next/script
in the server build by default: #40013next/future/image
to use svg blur placeholder duringnext dev
: #39992<noscript>
fromnext/future/image
: #40075filePath
being wrongly stringified: #40070alt
to required innext/future/image
: #40136next dev
andnext start
: #40118next/future/image
,remotePatterns
,unoptimized
: #40142@vercel/nft@0.22.1
: #40164next/config
: #40224next/future/image
to support onlywidth
or onlyheight
: #40278RemoveConsole
: #40296react/no-unknown-property
: #40331onLoadingComplete
fornext/future/image
to receive reference to<img>
: #40326Documentation Changes
next/future/image
docs about Known Browser Bugs: #39759exportPathMap
withgetStaticPaths
: #39813next/future/image
with details about computed aspect ratio: #39829largePageDataBytes
in warning docs: #39941script.md
: #40017pageExtensions
: #40016jest.config.js
: #40090remotePatterns
image config: #40350Example Changes
hideSourceMaps
: #40079image-component
example types: #40352Misc Changes
npm
version in issue validator: #38915Credits
Huge thanks to @stipsan, @ijjk, @timneutkens, @bennettdams, @shuding, @cherniavskii, @huozhi, @Brooooooklyn, @thatbeautifuldream, @Janpot, @MoosaSaadat, @alexcole, @HaNdTriX, @magic-akari, @balazsorban44, @styfle, @SukkaW, @kdy1, @sokra, @delbaoliveira, @puneetkathar1, @nkzawa, @Schniz, @greebl3, @kasperaamodt, @chaseignited, @masad-frost, @Kikobeats, @davewelsh, @MaedahBatool, @adrianbienias, @michaeloliverx, @arthurdenner, @sumiren, @migueloller, @hanneslund, @wyattjoh, @kwonoj, @boredland, @simongavelin, @esbenam, @theMosaad, @jleclanche, @leerob, @AdilAmanat, @souporserious, @ykdojo, @sanjaiyan-dev, @yoannmoinet, @thomasballinger, @titusdmoore, @jferrettiboke, @Dueen, @dunglas, @KenAKAFrosty, @wbinnssmith, @schehata, @remorses, @visnup, @Nutlope, @yhay81, @hiro0218, @avigoldman, @feugy, @jeferson-sb, @lobsterkatie, @atcastle, @bcheidemann, @Will956, @orionmiz, @S0UPernova, @cvbuelow, and @leonzalion for helping!
v12.2.6
Compare Source
v12.2.5
Compare Source
Core Changes
next/future/image
alt text: #39366eslint-plugin-eslint-plugin
to ensureeslint-plugin-next
rules follow ESLint rule best practices along with enforcing some consistency.: #37920--output-file
flag: #36420Documentation Changes
context.query
ingetServerSideProps()
: #39422router.prefetch
documentation to includelocale
option: #39442Example Changes
Misc Changes
Credits
Huge thanks to @pthomas931, @madmed88, @sanjaiyan-dev, @balazsorban44, @DonghyukJacobJang, @ijjk, @chaiwattsw, @styfle, @dunglas, @ahkhanjani, @promer94, @terrierscript, @shawncal, @insik-han, @QuiiBz, @ykzts, @JoshuaKGoldberg, @lucasassisrosa, @dikwickley, @Brooooooklyn, @sicarius97, @FourwingsY, @manovotny, @SukkaW, @pepoeverton, @jdeniau, @sumiren, @anthonyshew, @pekarja5, @huozhi, @leerob, @fediev, @atcastle, @shuding, @feugy, @jonohewitt, @zakiego, @Schniz, @timneutkens, @wyattjoh, [@MaedahBatool](https://redirect.github.
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.