Read the docs
TI-2015-07617 Aliases CVE-2015-9238GHSA-h9x2-5rm7-x4gm

Incorrect comparison in HackerOne secure-compare node module

Priority LOW 27CWE-697Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.0 · NVD. Fix status from CNA and 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.

Why it matters now

EPSS 0.01477 74th percentileScored 2026-11-07
Fix Fixed secure-compare (npm): 3.0.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
HackerOnesecure-compare node moduleup to 3.0.0—No fix listedCNA
—secure-compare (npm)before 3.0.13.0.1Patch availableGHSA-h9x2-5rm7-x4gm
  • secure-compare node module VendorHackerOne Affected up to 3.0.0 Fixed in — No fix listed CNA
  • secure-compare (npm) Vendor— Affected before 3.0.1 Fixed in 3.0.1 Patch available GHSA-h9x2-5rm7-x4gm

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:secure-compare_project:secure-compare:*:*:*:*:*:node.js:*:*before 3.0.1VulnerableSecure-compare Project
  • cpe:2.3:a:secure-compare_project:secure-compare:*:*:*:*:*:node.js:*:* Versions before 3.0.1 Vulnerable ·Secure-compare Project

Remediation

  • Fix · GHSA-h9x2-5rm7-x4gm secure-compare (npm) Fixed in 3.0.1 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2015-9238
  2. 2026-10-03 Alias added: GHSA-h9x2-5rm7-x4gm

References

Advisory 3

Other 2

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences