Vulnerability in Vercel Next.js
CVE-2022-21721
Next.js is a React framework. Starting with version 12.0.0 and prior to version 12.0.9, vulnerable code could allow a bad actor to trigger a denial of service attack for anyone using i18n functionality. In order to be affected by this CVE, one must use next start or a custom server and the built-in i18n support. Deployments on Vercel, along with similar environments where invalid requests are filtered before reaching Next.js, are not affected. A patch has been released, `next@12.0.9`, that mitigates this issue. As a workaround, one may ensure `/${locale}/_next/` is blocked from reaching the Next.js instance until it becomes feasible to upgrade.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.022, 82.5th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (tmyymmt/docker-ansible-nginx-laravel-nextjs). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/vercel/next.js/security/advisories/GHSA-wr66-vrwm-5g5x (Third Party Advisory)
- github.com/vercel/next.js/pull/33503 (Patch, Third Party Advisory)
- github.com/vercel/next.js/releases/tag/v12.0.9 (Third Party Advisory, Release Notes)