CVE Tools
Track your stack

CVE-2017-3736

Exploitation likely. EPSS gives it a 10% chance of exploitation in the next 30 days. Fixed in 1.0.2m.

CVSS 3.06.5MediumEPSS percentile96th10% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix1.0.2mUpgrade to this build

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • OpensslAffected: ≥ 1.0.2, < 1.0.2mUpgrade to: 1.0.2mStated by: NVD
  • Red Hat Inc. Red Hat Enterprise LinuxAffected: 7Upgrade to: not statedStated by: BDU
  • Сообщество свободного программного обеспечения Debian GNU/LinuxAffected: 9Upgrade to: not statedStated by: BDU
  • Novell Inc. OpenSUSE LeapAffected: 42.2Upgrade to: not statedStated by: BDU
  • Novell Inc. Suse Linux Enterprise DesktopAffected: 12 SP3Upgrade to: not statedStated by: BDU

Versions as the sources state them. 9 more products have version data. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether your systems use OpenSSL older than 1.0.2m or 1.1.0g, and whether they run servers with persistent Diffie-Hellman settings.
  2. Upgrade OpenSSL to 1.0.2m or later on the 1.0.2 branch, or 1.1.0g or later on the 1.1.0 branch.
  3. If you use operating-system updates, install your vendor's OpenSSL security update instead of manually replacing system files.
  4. If an upgrade must wait, stop using persistent Diffie-Hellman parameters and use updated server encryption settings.
Vendor advisory Usually a quick update
Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and 1.1.0 before 1.1.0g. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. This only affects processors that support the BMI1, BMI2 and ADX extensions like Intel Broadwell (5th generation) and later or AMD Ryzen.

In plain language

Written by AI from the record

This affects older OpenSSL versions and is a low-priority concern for most small businesses because exploitation requires an uncommon, specific server setup on newer processors.

An x86_64 Montgomery-squaring carry-propagation defect can leak Diffie-Hellman private-key information through repeated network key exchanges on BMI1/BMI2/ADX-capable hosts using shared persistent DH parameters.

If you're affected

  • Private key information exposure
  • Encrypted traffic at risk
  • Server trust compromise

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

10% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

24 events over 3247 days, from the signal feeds we watch.

  1. EPSS band changelow → moderateepss band change
  2. EPSS band changemoderate → lowepss band change
  3. EPSS band changelow → moderateepss band change
  4. EPSS band changemoderate → lowepss band change
  5. EPSS band changelow → moderateepss band change
  6. EPSS band changemoderate → low

Affected products

And 4 more affected products. See all after sign-in

Technical detail

CVSS 3.0 vector

Open in the CVSS calculator

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Scored 6.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 29 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for OpenSUSE Leap, not every advisory.