Skip to main content
Public proof of conceptFix available

CVE-2015-3197

A public proof of concept exists; no exploitation attested.

  • Published2016-02-15
  • WeaknessCWE-200 · CWE-310

Am I 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
  1. 2016-02-1502:59CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub
  3. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block 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
OpenSSL
BranchAffectedFixed in
1.0= 1.0.1no fix published
1.0= 1.0.1ano fix published
1.0= 1.0.1bno fix published
1.0= 1.0.1cno fix published
1.0= 1.0.1dno fix published
1.0= 1.0.1eno fix published
1.0= 1.0.1fno fix published
1.0= 1.0.1gno fix published
1.0= 1.0.1hno fix published
1.0= 1.0.1ino fix published
1.0= 1.0.1jno fix published
1.0= 1.0.1kno fix published
Oracle peoplesoft enterprise peopletools
BranchAffectedFixed in
8.53= 8.53no fix published
8.54= 8.54no fix published
8.55= 8.55no fix published
Oracle exalogic infrastructure
BranchAffectedFixed in
1.0= 1.0no fix published
2.0= 2.0no fix published

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

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?

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.

Is CVE-2015-3197 actively exploited?

Active exploitation of CVE-2015-3197 has not been confirmed. Its EPSS score was 10.7% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2015-3197?

CVE-2015-3197 has a CVSS v3 base score of 5.9 (MEDIUM severity), with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.

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