CVE-2018-6184: Path Traversal
Published Jan 24, 2018
·Updated
ZEIT Next.js 4 before 4.2.3 has Directory Traversal under the /next request namespace.
Affected Software
17 affected components
ZEIT Next.js=4.0.0
ZEIT Next.js=4.0.1
ZEIT Next.js=4.0.2
ZEIT Next.js=4.0.3
ZEIT Next.js=4.0.4
ZEIT Next.js=4.0.5
ZEIT Next.js=4.1.0
ZEIT Next.js=4.1.1
ZEIT Next.js=4.1.2
ZEIT Next.js=4.1.3
ZEIT Next.js=4.1.4
ZEIT Next.js=4.1.4-canary_1
ZEIT Next.js=4.1.4-canary_2
ZEIT Next.js=4.2.0
ZEIT Next.js=4.2.0-canary_1
ZEIT Next.js=4.2.1
ZEIT Next.js=4.2.2
Event History
Jan 24, 2018
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Data Sourced
via NVD·10:29 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2018-6184?
CVE-2018-6184 has been classified with a high severity due to its potential for directory traversal attacks.
2
How do I fix CVE-2018-6184?
To fix CVE-2018-6184, upgrade Next.js to version 4.2.3 or later.
3
What versions of Next.js are affected by CVE-2018-6184?
CVE-2018-6184 affects Next.js versions from 4.0.0 to 4.2.2.
4
What is directory traversal in the context of CVE-2018-6184?
Directory traversal in CVE-2018-6184 allows an attacker to access files outside the intended directory paths.
5
Is there a patch available for CVE-2018-6184?
Yes, the patch for CVE-2018-6184 is included in Next.js version 4.2.3.