Is CVE-2020-15095 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2020-15095 being exploited in the wild.

How severe is CVE-2020-15095?

Low severity, with a CVSS score of 3.1, published 7 July 2020.

Is there a fix for CVE-2020-15095?

A patch was published on 2020-07-07: version 6.14.6 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2020-15095 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2020-15095?

Check whether you run npm (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-15095: npm CLI information exposure through logs

CVE-2020-15095 · Severity: low · CVSS 3.1 · Published 2020-07-07

The npm CLI package manager inadvertently logs unredacted authentication credentials when processing registry URLs containing embedded passwords. An attacker with local access to log files could extract these credentials and gain unauthorized access to private npm packages or registries, potentially compromising supply chain security and sensitive development resources.

Technologies: npm (npm). Vendors: npm.

Quick answers

Is CVE-2020-15095 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2020-15095 being exploited in the wild.
How severe is CVE-2020-15095?: Low severity, with a CVSS score of 3.1, published 7 July 2020.
Which products and versions are affected?: npm (npm) prior to 6.14.6.
Is there a fix for CVE-2020-15095?: A patch was published on 2020-07-07: version 6.14.6 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2020-15095 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2020-15095?: Check whether you run npm (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an information exposure flaw (CWE-532) in npm CLI versions prior to 6.14.6. The CLI fails to redact password values from URLs matching the pattern <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>. Credentials are exposed both to stdout and in log files generated by the tool. Attack requires local file system access to read generated logs. An attacker can retrieve plaintext authentication credentials and use them for unauthorized package registry access. The vulnerability was patched in version 6.14.6.

Affected products

npm npm prior to 6.14.6

Identifiers

CVE-2020-15095
GHSA-93f3-23rq-pjfp

Timeline

2020-07-07: disclosed
2020-07-07: patched: version 6.14.6 released

References

https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.