utahcityfinder on Node.js URL path traversal

Summaryinfo

A vulnerability classified as critical has been found in utahcityfinder on Node.js. This impacts an unknown function of the component URL Handler. Performing a manipulation with the input ../ results in path traversal. This vulnerability is cataloged as CVE-2017-16173. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in utahcityfinder on Node.js (JavaScript Library) (version now known). It has been classified as critical. This affects some unknown processing of the component URL Handler. The manipulation with the input value ../ leads to a path traversal vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:

utahcityfinder constructs lists of Utah cities with a certiain prefix. utahcityfinder is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url.

The bug was discovered 10/02/2017. The weakness was shared 06/07/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2017-16173 since 10/29/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 247 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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• JavaScript Library

Name

• utahcityfinder

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion