CVE-2015-9238GHSA-H9X2-5RM7-X4GM
secure-compare 3.0.0 and below do not actually compare two strings properly.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- HackerOne secure-compare node module
through 3.0.0
- secure-comparenpm
fixed in 3.0.1