What is the CVSS score of CVE-2017-16877?

CVE-2017-16877 has a CVSS 3.0 base score of 7.5 (High). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 80.8%.

Is there a public PoC exploit available for CVE-2017-16877?

Yes, a public proof-of-concept exploit is available for CVE-2017-16877. Prioritise patching immediately. EPSS: 80.8%.

Is there a patch available for CVE-2017-16877?

Yes, a patch is available for CVE-2017-16877. Update the affected software to the latest version immediately.

Next.js CVE-2017-16877

HIGH

Path Traversal (CWE-22)

2017-11-17 cve@mitre.org

Path Traversal Next.js

7.5

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Nov 17, 2017 - 17:29 cve.org

HIGH 7.5

DescriptionCVE.org

ZEIT Next.js before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing attackers to obtain sensitive information.

AnalysisAI

ZEIT Next.js before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing attackers to obtain sensitive information. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and EPSS exploitation probability 80.8%.

Technical ContextAI

This vulnerability is classified as Path Traversal (CWE-22), which allows attackers to access files and directories outside the intended path. ZEIT Next.js before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing attackers to obtain sensitive information. Affected products include: Zeit Next.Js. Version information: before 2.4.1.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate and canonicalize file paths. Use chroot or sandboxing. Reject input containing path separators or '../' sequences.