gh-pages up to 0.9.0 on Node.js Logging Credentials log file

Summaryinfo

A vulnerability classified as problematic has been found in gh-pages up to 0.9.0 on Node.js. The impacted element is an unknown function of the component Logging. This manipulation causes log file (Credentials). This vulnerability is handled as CVE-2016-10526. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in gh-pages up to 0.9.0 on Node.js (JavaScript Library). It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component Logging. The manipulation with an unknown input leads to a log file vulnerability (Credentials). The CWE definition for the vulnerability is CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. As an impact it is known to affect confidentiality. The summary by CVE is:

A common setup to deploy to gh-pages on every commit via a CI system is to expose a github token to ENV and to use it directly in the auth part of the url. In module versions < 0.9.1 the auth portion of the url is outputted as part of the grunt tasks logging function. If this output is publicly available then the credentials should be considered compromised.

The bug was discovered 03/16/2016. The weakness was released 05/31/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2016-10526 since 10/29/2017. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

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

Upgrading to version 0.9.1 eliminates this vulnerability.

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

Productinfo

Type

• JavaScript Library

Name

• gh-pages

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9.0

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