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
Path to vulnerable library: /node_modules/next/package.json
Dependency Hierarchy:
❌ next-9.5.4.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue.
mend-for-github-combot
changed the title
CVE-2021-43803 (High) detected in next-9.5.4.tgz
CVE-2021-43803 (High) detected in next-9.5.4.tgz - autoclosed
May 19, 2024
CVE-2021-43803 - High Severity Vulnerability
The React Framework
Library home page: https://registry.npmjs.org/next/-/next-9.5.4.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/next/package.json
Dependency Hierarchy:
Found in base branch: main
Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue.
Publish Date: 2021-12-10
URL: CVE-2021-43803
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-25mp-g6fv-mqxx
Release Date: 2021-12-10
Fix Resolution: 11.1.2-canary.0
⛑️ Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: