CVE-2015-9238 json
Insecure Comparison in secure-compare
published 2018-05-31 8 y ago modified 2026-06-17 4 mo ago also GHSA-h9x2-5rm7-x4gm , EUVD-2019-0540
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm secure-compare 3.0.1
- secure-compare_project secure-compare 3.0.1
- github.com/vadimdemedes/secure-compare@dd1ff1a commit
- github.com/vdemedes/secure-compare#1 pull request
Exploit prediction
1.45% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | secure-compare | <3.0.1 |
3.0.1 |
Affected products
- HackerOne secure-compare node module
Classification
References
-
github.com
/vdemedes/secure-compare/pull/1
web, third-party-advisory
-
github.com
/vadimdemedes/secure-compare/commit/dd1ff1ac0122de7e0af4f00c61ed73261062394a
web
-
nodesecurity.io
/advisories/50
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2015-9238
advisory
-
npmjs.com
/advisories/50
web
Sources
- CVE List CVE-2015-9238
- GitHub Advisory GHSA-h9x2-5rm7-x4gm
- NVD CVE-2015-9238
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.