resolve-path up to 1.3.x on Node.js Special Char path traversal

Summaryinfo

A vulnerability has been found in resolve-path up to 1.3.x on Node.js and classified as critical. The affected element is an unknown function. The manipulation as part of Special Char leads to path traversal. This vulnerability is listed as CVE-2018-3732. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in resolve-path up to 1.3.x on Node.js (JavaScript Library). It has been rated as critical. This issue affects an unknown part. The manipulation as part of a Special Char leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, and integrity. The summary by CVE is:

resolve-path node module before 1.4.0 suffers from a Path Traversal vulnerability due to lack of validation of paths with certain special characters, which allows a malicious user to read content of any file with known path.

The bug was discovered 03/08/2018. The weakness was presented 06/07/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-3732 since 12/28/2017. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 90 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 1.4.0 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• JavaScript Library

Name

• resolve-path

Version

• 1.0
• 1.1
• 1.2
• 1.3

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion