Kurz gesagt
- CVE-2021-37699 ist eine Schwachstelle (MITTEL (CVSS 6.1)) in next.js (vercel), next.
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 1.0%, höher als bei 63.8% aller Schwachstellen.
- Abhilfe: auf 11.1.0 oder neuer aktualisieren.
| Package | Affected versions | Patched versions |
|---|
| next.js | ≥ 10.0.5, ≤ 10.2.0≥ 11.0.0, ≤ 11.0.1
| No fix yet |
| next npm | ≥ 0.9.9, < 11.1.0
| 11.1.0
|
Description
Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when pages/_error.js was statically generated, allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although it can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.
Impact
- Affected: Users of Next.js between
10.0.5 and 10.2.0
- Affected: Users of Next.js between
11.0.0 and 11.0.1 using pages/_error.js without getInitialProps
- Affected: Users of Next.js between
11.0.0 and 11.0.1 using pages/_error.js and next export
- Not affected: Deployments on Vercel (vercel.com) are not affected
- Not affected: Deployments with
pages/404.js
- Note that versions prior to 0.9.9 package
next npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.
We recommend upgrading to the latest version of Next.js to improve the overall security of your application.
Patches
https://github.com/vercel/next.js/releases/tag/v11.1.0
NVD description
Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when pages/_error.js was statically generated allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain. We recommend everyone to upgrade regardless of whether you can reproduce the issue or not. The issue has been patched in release 11.1.0.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free