Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2020-15095: Sensitive information exposure through logs in npm cli

Noroxi assessment

Priority: Monitor (action score 17/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.40% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: nodejs-nodemon (AlmaLinux:8) 1.18.3-1.module_el8.3.0+2047+b07ac28e, 1.18.3-1.module_el8.3.0+2023+d2377ea3; nodejs-packaging (AlmaLinux:8) 17-3.module_el8.3.0+2023+d2377ea3, 17-3.module_el8.4.0+2521+c668cc9f, 17-3.module_el8.4.0+2224+b07ac28e; npm (Debian:12) 6.14.6+ds-1.
  • Mentioned 4 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to nodejs-nodemon (AlmaLinux:8) 1.18.3-1.module_el8.3.0+2047+b07ac28e, 1.18.3-1.module_el8.3.0+2023+d2377ea3; nodejs-packaging (AlmaLinux:8) 17-3.module_el8.3.0+2023+d2377ea3, 17-3.module_el8.4.0+2521+c668cc9f, 17-3.module_el8.4.0+2224+b07ac28e; npm (Debian:12) 6.14.6+ds-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like "<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>". The password value is not redacted and is printed to stdout and also to any generated log files.

MediumCVSS 4.4 · v3.1—No exploit Fix available
Published
Jul 7, 2020
Updated
Jun 16, 2026
EPSS
0.4% · 34th percentile

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CNA vs NVD score

NVD
4.4
CNA · GitHub_M
4.4
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-15095

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for npmjs records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
npmjsnpm
opensuseleap
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora33
  • npmjs npmbefore 6.14.6
  • opensuse leap15.1
  • opensuse leap15.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • npm cli

    • < 6.14.6affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8nodejs-nodemonbefore 1.18.3-1.module_el8.3.0+2047+b07ac28e1.18.3-1.module_el8.3.0+2047+b07ac28e
AlmaLinux:8nodejs-nodemonbefore 1.18.3-1.module_el8.3.0+2023+d2377ea31.18.3-1.module_el8.3.0+2023+d2377ea3
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.3.0+2023+d2377ea317-3.module_el8.3.0+2023+d2377ea3
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.4.0+2521+c668cc9f17-3.module_el8.4.0+2521+c668cc9f
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.4.0+2224+b07ac28e17-3.module_el8.4.0+2224+b07ac28e
Debian:12npmbefore 6.14.6+ds-16.14.6+ds-1
npmnpmbefore 6.14.66.14.6
openSUSE:Leap 15.1nodejs8before 8.17.0-lp151.2.21.18.17.0-lp151.2.21.1
openSUSE:Leap 15.2nodejs10before 10.22.1-lp152.2.6.110.22.1-lp152.2.6.1
openSUSE:Leap 15.2nodejs12before 12.18.4-lp152.3.6.112.18.4-lp152.3.6.1
openSUSE:Tumbleweednodejs14before 14.17.5-1.214.17.5-1.2
Red Hat:enterprise_linux:8::appstreamnodejsbefore 1:10.23.1-1.module+el8.3.0+9502+012d8a971:10.23.1-1.module+el8.3.0+9502+012d8a97
Red Hat:enterprise_linux:8::appstreamnodejsbefore 1:12.18.4-2.module+el8.2.0+8361+192e434e1:12.18.4-2.module+el8.2.0+8361+192e434e
Red Hat:enterprise_linux:8::appstreamnodejs-debuginfobefore 1:12.18.4-2.module+el8.2.0+8361+192e434e1:12.18.4-2.module+el8.2.0+8361+192e434e
Red Hat:enterprise_linux:8::appstreamnodejs-debuginfobefore 1:10.23.1-1.module+el8.3.0+9502+012d8a971:10.23.1-1.module+el8.3.0+9502+012d8a97
Red Hat:enterprise_linux:8::appstreamnodejs-debugsourcebefore 1:12.18.4-2.module+el8.2.0+8361+192e434e1:12.18.4-2.module+el8.2.0+8361+192e434e
Red Hat:enterprise_linux:8::appstreamnodejs-debugsourcebefore 1:10.23.1-1.module+el8.3.0+9502+012d8a971:10.23.1-1.module+el8.3.0+9502+012d8a97
Red Hat:enterprise_linux:8::appstreamnodejs-develbefore 1:12.18.4-2.module+el8.2.0+8361+192e434e1:12.18.4-2.module+el8.2.0+8361+192e434e
Red Hat:enterprise_linux:8::appstreamnodejs-develbefore 1:10.23.1-1.module+el8.3.0+9502+012d8a971:10.23.1-1.module+el8.3.0+9502+012d8a97
Red Hat:enterprise_linux:8::appstreamnodejs-docsbefore 1:12.18.4-2.module+el8.2.0+8361+192e434e1:12.18.4-2.module+el8.2.0+8361+192e434e
Red Hat:enterprise_linux:8::appstreamnodejs-docsbefore 1:10.23.1-1.module+el8.3.0+9502+012d8a971:10.23.1-1.module+el8.3.0+9502+012d8a97
Red Hat:enterprise_linux:8::appstreamnodejs-full-i18nbefore 1:12.18.4-2.module+el8.2.0+8361+192e434e1:12.18.4-2.module+el8.2.0+8361+192e434e
Red Hat:enterprise_linux:8::appstreamnodejs-full-i18nbefore 1:10.23.1-1.module+el8.3.0+9502+012d8a971:10.23.1-1.module+el8.3.0+9502+012d8a97
Red Hat:enterprise_linux:8::appstreamnodejs-nodemonbefore 0:1.18.3-1.module+el8.1.0+3369+37ae6a450:1.18.3-1.module+el8.1.0+3369+37ae6a45

+30

Same product

npmjs: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-43616The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differ
    40Plan
  • CVE-2019-16776Unauthorized File Access in npm CLI before before version 6.13.3
    33Monitor
  • CVE-2022-29244npm packing does not respect root-level ignore files in workspaces
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2018-7408Feb 22, 2018 · An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upg
    31Monitor
  • ← EarlierCVE-2019-16777Dec 12, 2019 · Arbitrary File Overwrite in npm CLI
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:nodejs-nodemon1.18.3-1.module_el8.3.0+2023+d2377ea3 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging17-3.module_el8.4.0+2224+b07ac28e · AlmaLinux:8Package registry (OSV)
debian:npm6.14.6+ds-1 · Debian:12Package registry (OSV)
npm:npm6.14.6Package registry (OSV)
opensuse:nodejs1010.22.1-lp152.2.6.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:nodejs1212.18.4-lp152.3.6.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:nodejs1414.17.5-1.2 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:nodejs88.17.0-lp151.2.21.1 · openSUSE:Leap 15.1Package registry (OSV)
red hat:nodejs1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-debuginfo1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-debugsource1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-devel1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-docs1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-full-i18n1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-nodemon0:1.18.3-1.module+el8.1.0+3369+37ae6a45 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-packaging0:17-3.module+el8.1.0+3369+37ae6a45 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:npm1:6.14.6-1.12.18.4.2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:rh-nodejs12-nodejs0:12.18.4-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-debuginfo0:12.18.4-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-devel0:12.18.4-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
rocky linux:nodejs-nodemon0:1.18.3-1.module+el8.3.0+101+f84c7154 · Rocky Linux:8Package registry (OSV)
rocky linux:nodejs-packaging0:17-3.module+el8.3.0+101+f84c7154 · Rocky Linux:8Package registry (OSV)
suse:nodejs1010.22.1-1.30.1 · SUSE:Linux Enterprise Module for Web and Scripting 12Package registry (OSV)
suse:nodejs1212.18.4-1.20.1 · SUSE:Linux Enterprise Module for Web and Scripting 12Package registry (OSV)
suse:nodejs88.17.0-10.3.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-532 · Insertion of Sensitive Information into Log File

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records