CVE-2015-9238: secure-compare 3.0.0 and below do not actually compare two strings properly
CVE-2015-9238 is a medium-severity flaw (CVSS 5.3) affecting secure-compare. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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 this priority
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2015-9238?
secure-compare: upgrade to 3.0.1. Exact commands for each OS are on this page.
Is CVE-2015-9238 being exploited?
CVE-2015-9238 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2015-9238 affect?
CVE-2015-9238 affects secure-compare. Severity is medium (CVSS 5.3). 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.
How urgent is CVE-2015-9238?
Priority 42/100. Remotely exploitable, no login, no user action