You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Next.js is a React framework for building full-stack web applications. By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a Cache-Control: s-maxage=1, stale-while-revalidate header which some upstream CDNs may cache as well. To be potentially affected all of the following must apply: 1. Next.js between 13.5.1 and 14.2.9, 2. Using pages router, & 3. Using non-dynamic server-side rendered routes e.g. pages/dashboard.tsx not pages/blog/[slug].tsx. This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not. There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.
Next.js is a React Framework for the Web. Cersions on the 10.x, 11.x, 12.x, 13.x, and 14.x branches before version 14.2.7 contain a vulnerability in the image optimization feature which allows for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption. Neither the next.config.js file that is configured with images.unoptimized set to true or images.loader set to a non-default value nor the Next.js application that is hosted on Vercel are affected. This issue was fully patched in Next.js 14.2.7. As a workaround, ensure that the next.config.js file has either images.unoptimized, images.loader or images.loaderFile assigned.
mend-bolt-for-githubbot
changed the title
next-14.1.3.tgz: 1 vulnerabilities (highest severity is: 7.5)
next-14.1.3.tgz: 2 vulnerabilities (highest severity is: 7.5)
Oct 15, 2024
Vulnerable Library - next-14.1.3.tgz
Library home page: https://registry.npmjs.org/next/-/next-14.1.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2024-46982
Vulnerable Library - next-14.1.3.tgz
Library home page: https://registry.npmjs.org/next/-/next-14.1.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
Next.js is a React framework for building full-stack web applications. By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a
Cache-Control: s-maxage=1, stale-while-revalidate
header which some upstream CDNs may cache as well. To be potentially affected all of the following must apply: 1. Next.js between 13.5.1 and 14.2.9, 2. Using pages router, & 3. Using non-dynamic server-side rendered routes e.g.pages/dashboard.tsx
notpages/blog/[slug].tsx
. This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not. There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.Publish Date: 2024-09-17
URL: CVE-2024-46982
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-gp8f-8m3g-qvj9
Release Date: 2024-09-17
Fix Resolution: 14.3.0-canary.0
Step up your Open Source Security Game with Mend here
CVE-2024-47831
Vulnerable Library - next-14.1.3.tgz
Library home page: https://registry.npmjs.org/next/-/next-14.1.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
Next.js is a React Framework for the Web. Cersions on the 10.x, 11.x, 12.x, 13.x, and 14.x branches before version 14.2.7 contain a vulnerability in the image optimization feature which allows for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption. Neither the
next.config.js
file that is configured withimages.unoptimized
set totrue
orimages.loader
set to a non-default value nor the Next.js application that is hosted on Vercel are affected. This issue was fully patched in Next.js14.2.7
. As a workaround, ensure that thenext.config.js
file has eitherimages.unoptimized
,images.loader
orimages.loaderFile
assigned.Publish Date: 2024-10-14
URL: CVE-2024-47831
CVSS 3 Score Details (5.9)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-g77x-44xx-532m
Release Date: 2024-10-14
Fix Resolution: 14.3.0-canary.0
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: