- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Versions of `next` prior to 5.1.0 are vulnerable to Remote Code Execution. The `/path:` route fails to properly sanitize input and passes it to a `require()` call. This allows attackers to execute JavaScript code on the server. Note that prior version 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.
## Recommendation
Upgrade to version 5.1.0.
Patch / fix
- npm next 5.1.0
Is GHSA-5vj8-3v2h-h38v 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | next | >=0.9.9, <5.1.0 |
5.1.0 |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
github.com
/vercel/next.js
package
-
npmjs.com
/advisories/1538
web
Sources
- GitHub Advisory GHSA-5vj8-3v2h-h38v
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.