CVE-2015-3197
A public proof of concept exists; no exploitation attested.
- Published2016-02-15
- WeaknessCWE-200 · CWE-310
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
ssl/s2_srvr.c in OpenSSL 1.0.1 before 1.0.1r and 1.0.2 before 1.0.2f does not prevent use of disabled ciphers, which makes it easier for man-in-the-middle attackers to defeat cryptographic protection mechanisms by performing computations on SSLv2 traffic, related to the get_client_master_key and get_client_hello functions.
Timeline
dates in UTC- 2016-02-1502:59CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2015-3197?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2015-3197?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.0 | = 1.0.1 | no fix published | NVD |
| 1.0 | = 1.0.1a | no fix published | NVD |
| 1.0 | = 1.0.1b | no fix published | NVD |
| 1.0 | = 1.0.1c | no fix published | NVD |
| 1.0 | = 1.0.1d | no fix published | NVD |
| 1.0 | = 1.0.1e | no fix published | NVD |
| 1.0 | = 1.0.1f | no fix published | NVD |
| 1.0 | = 1.0.1g | no fix published | NVD |
| 1.0 | = 1.0.1h | no fix published | NVD |
| 1.0 | = 1.0.1i | no fix published | NVD |
| 1.0 | = 1.0.1j | no fix published | NVD |
| 1.0 | = 1.0.1k | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.53 | = 8.53 | no fix published | NVD |
| 8.54 | = 8.54 | no fix published | NVD |
| 8.55 | = 8.55 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.0 | = 1.0 | no fix published | NVD |
| 2.0 | = 2.0 | no fix published | NVD |
3 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- www.openssl.orgVendor Advisory
- www.oracle.comPatch
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 1 repository, unverifiedTrinadh465/OpenSSL-1_0_1g_CVE-2015-3197 PoC-in-GitHub
Sources
- NVDCVSS 3.05.9read 2026-10-23
- NVDCVSS 2.04.3read 2026-10-23
- NVDweakness (CWE)CWE-200, CWE-310read 2026-10-23
- FIRST EPSSEPSS score10.7 %read 2026-10-23
- PoC-in-GitHubproof of concept1read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2016-02-15
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2015-3197?
Is CVE-2015-3197 actively exploited?
What is the CVSS score for CVE-2015-3197?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.