ritp on Node.js URL path traversal

Summaryinfo

A vulnerability labeled as critical has been found in ritp on Node.js. Affected by this issue is some unknown functionality of the component URL Handler. Executing a manipulation with the input ../ can lead to path traversal. The identification of this vulnerability is CVE-2017-16198. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability has been found in ritp on Node.js (JavaScript Library) (the affected version unknown) and classified as critical. This vulnerability affects an unknown part of the component URL Handler. The manipulation with the input value ../ leads to a path traversal vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, and integrity. CVE summarizes:

ritp is a static web server. ritp is vulnerable to a directory traversal issue whereby an attacker can gain access to the file system by placing ../ in the URL. Access is restricted to files with a file extension, so files such as /etc/passwd are not accessible.

The bug was discovered 10/04/2017. The weakness was shared 06/07/2018 (Website). The advisory is shared for download at github.com. This vulnerability was named CVE-2017-16198 since 10/29/2017. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1006.

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

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• JavaScript Library

Name

• ritp

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion