Description
Next.js before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing attackers to obtain sensitive information.
Basic information
- Type
- reviewed
- Severity
- high
- Advisory on GitHub
- Open advisory ↗
- Repository advisory
- —
- Source code
- Browse source ↗
- Published (advisory)
- 2017-12-05 02:04:14 UTC
- Updated
- 2024-04-22 19:49:39 UTC
- GitHub reviewed
- 2020-06-16 20:54:56 UTC
- NVD published
- 2017-11-17
EPSS Score
| Score |
Percentile |
|
80.76%
|
99.15% |
CVSS Scores
| Base score |
Version |
Severity |
Vector |
|
7.5
|
3.0 |
—
|
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Click to expand
- Attack vector (AV:N)
- Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
- Attack complexity (AC:L)
- Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
- Privileges required (PR:N)
- No account or special rights needed—anonymous or random user is enough.
- User interaction (UI:N)
- Nobody has to click “OK” or open a trap file; it can work without a victim helping.
- Scope (S:U)
- Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
- Confidentiality (C:H)
- Serious risk that confidential data gets exposed in a big way.
- Integrity (I:N)
- Data isn’t meaningfully altered or forged.
- Availability (A:N)
- Service keeps running; no real outage angle.
|
CWEs
| CWE id |
Name |
|
CWE-22
|
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') |
Affected packages (1)
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem |
Package |
Vulnerable range |
First patched |
Vulnerable functions |
| npm |
next |
>= 1.0.0, < 2.4.1 |
2.4.1 |
—
|
cvelogic
Threat Intelligence