CVE-2015-9238

Description

secure-compare 3.0.0 and below do not actually compare two strings properly. compare was actually comparing the first argument with itself, meaning the check passed for any two strings of the same length.

Severity
MEDIUM
CVSS v3
5.3
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N · source nvd
Exploit chance (EPSS)
1.449%
chance of exploitation in the next 30 days
higher than 73.8% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2018-05-31Published by the CNA20:00 UTC
  2. 2019-06-03GitHub advisory published (GHSA-h9x2-5rm7-x4gm)368 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-h9x2-5rm7-x4gm, affected packages:

PackageVulnerable versionsFixed in
npm secure-comparebefore 3.0.13.0.1

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
secure-compare_project secure-comparebefore 3.0.1fixed in 3.0.13.0.1

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources