CVE-2022-21721 json
DOS Vulnerability in next.js
published 4y ago modified last mo. also EUVD-2022-0727 , GHSA-wr66-vrwm-5g5x
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm next 12.0.9
- vercel next.js 12.0.9
- github.com/vercel/next.js#33503 pull request
- github.com/vercel/next.js/releases/tag/v12.0.9 release
Is CVE-2022-21721 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | next | >=12.0.0, <12.0.9 |
12.0.9 |
Classification
- Weakness
- Technology feeds
References
-
github.com
/vercel/next.js/pull/33503
web, patch, third-party-advisory
-
github.com
/vercel/next.js/security/advisories/GHSA-wr66-vrwm-5g5x
web, third-party-advisory, advisory
-
github.com
/vercel/next.js/releases/tag/v12.0.9
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-21721
advisory
-
github.com
/vercel/next.js
package
Sources
- CVE List CVE-2022-21721
- GitHub Advisory GHSA-wr66-vrwm-5g5x
- NVD CVE-2022-21721
- Maintainer advisory GHSA-wr66-vrwm-5g5x
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of vercel/next.js published their own advisory on GitHub. Reviewed sources take precedence over it.