next-14.2.8.tgz: 4 vulnerabilities (highest severity is: 7.5)

[mend-bolt-for-github]

Vulnerable Library - next-14.2.8.tgz

The React Framework

Library home page: https://registry.npmjs.org/next/-/next-14.2.8.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Found in HEAD commit: 9ae87edd1101b0d1d4b4bc9dce9980b2b97bdb67

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (next version)	Remediation Possible**
CVE-2024-51479	High	7.5	next-14.2.8.tgz	Direct	next - 14.2.15	❌
CVE-2024-46982	High	7.5	next-14.2.8.tgz	Direct	next - 13.5.7,14.2.10	❌
CVE-2024-56332	Medium	5.3	next-14.2.8.tgz	Direct	next - 13.5.8,14.2.21,15.1.2	❌
CVE-2024-55565	Medium	4.3	nanoid-3.3.7.tgz	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2024-51479

Vulnerable Library - next-14.2.8.tgz

The React Framework

Library home page: https://registry.npmjs.org/next/-/next-14.2.8.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

• ❌ next-14.2.8.tgz (Vulnerable Library)

Found in HEAD commit: 9ae87edd1101b0d1d4b4bc9dce9980b2b97bdb67

Found in base branch: dev

Vulnerability Details

Next.js is a React framework for building full-stack web applications. In affected versions 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: * [Not affected] "https://example.com/" * [Affected] "https://example.com/foo" * [Not affected] "https://example.com/foo/bar". This issue is 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. There are no official workarounds for this vulnerability.

Publish Date: 2024-12-17

URL: CVE-2024-51479

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-7gfc-8cq8-jh5f

Release Date: 2024-12-17

Fix Resolution: next - 14.2.15

Step up your Open Source Security Game with Mend here

CVE-2024-46982

Vulnerable Library - next-14.2.8.tgz

The React Framework

Library home page: https://registry.npmjs.org/next/-/next-14.2.8.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

• ❌ next-14.2.8.tgz (Vulnerable Library)

Found in HEAD commit: 9ae87edd1101b0d1d4b4bc9dce9980b2b97bdb67

Found in base branch: dev

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 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.

Publish Date: 2024-09-17

URL: CVE-2024-46982

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-gp8f-8m3g-qvj9

Release Date: 2024-09-17

Fix Resolution: next - 13.5.7,14.2.10

Step up your Open Source Security Game with Mend here

CVE-2024-56332

Vulnerable Library - next-14.2.8.tgz

The React Framework

Library home page: https://registry.npmjs.org/next/-/next-14.2.8.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

• ❌ next-14.2.8.tgz (Vulnerable Library)

Found in HEAD commit: 9ae87edd1101b0d1d4b4bc9dce9980b2b97bdb67

Found in base branch: dev

Vulnerability Details

Next.js is a React framework for building full-stack web applications. Starting in version 13.0.0 and prior to versions 13.5.8, 14.2.21, and 15.1.2, Next.js is vulnerable to a Denial of Service (DoS) attack that allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution. This vulnerability can also be used as a Denial of Wallet (DoW) attack when deployed in providers billing by response times. (Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time.). Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing. This is the same issue as if the incoming HTTP request has an invalid "Content-Length" header or never closes. If the host has no other mitigations to those then this vulnerability is novel. This vulnerability affects only Next.js deployments using Server Actions. The issue was resolved in Next.js 13.5.8, 14.2.21, and 15.1.2. We recommend that users upgrade to a safe version. There are no official workarounds.

Publish Date: 2025-01-03

URL: CVE-2024-56332

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-7m27-7ghc-44w9

Release Date: 2025-01-03

Fix Resolution: next - 13.5.8,14.2.21,15.1.2

Step up your Open Source Security Game with Mend here

CVE-2024-55565

Vulnerable Library - nanoid-3.3.7.tgz

Library home page: https://registry.npmjs.org/nanoid/-/nanoid-3.3.7.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

• next-14.2.8.tgz (Root Library)
  • postcss-8.4.31.tgz
    • ❌ nanoid-3.3.7.tgz (Vulnerable Library)

Found in HEAD commit: 9ae87edd1101b0d1d4b4bc9dce9980b2b97bdb67

Found in base branch: dev

Vulnerability Details

nanoid (aka Nano ID) before 5.0.9 mishandles non-integer values. 3.3.8 is also a fixed version.

Publish Date: 2024-12-09

URL: CVE-2024-55565

CVSS 3 Score Details (4.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: Low
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2024-55565

Release Date: 2024-12-09

Fix Resolution: nanoid - 3.3.8,5.0.9

Step up your Open Source Security Game with Mend here