Skip to content
Fencer Intel
medium 5.0

CVE-2012-2686 json

crypto/evp/e_aes_cbc_hmac_sha1.c in the AES-NI functionality in the TLS 1.1 and 1.2 implementations in OpenSSL 1.0.1 before 1.0.1d allows r…

published 2013-02-08 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2668

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
39.6%
EPSS 39.6% chance of exploitation in 30 days, percentile 98%
public exploits
1
Metasploit

Summary

crypto/evp/e_aes_cbc_hmac_sha1.c in the AES-NI functionality in the TLS 1.1 and 1.2 implementations in OpenSSL 1.0.1 before 1.0.1d allows remote attackers to cause a denial of service (application crash) via crafted CBC data.

Patch / fix

  • openssl Debian 14, Debian 13, Debian 12 1.0.1e-1

debian advisories DEBIAN-CVE-2012-2686

  • openssl-1_1 openSUSE Tumbleweed 1.1.1l-1.2

opensuse advisories openSUSE-SU-2024:11127-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-2686 updated cvss 5.0

openssl: DoS due to improper handling of CBC ciphersuites in TLS 1.1/1.2 on AES-NI supporting platforms

  • Red Hat Enterprise Linux 5 openssl, openssl097a Red Hat Enterprise Linux 6 openssl, openssl098e, openssl-perl
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (Metasploit auxiliary/dos/ssl/openssl_aesni)
  2. Published

Exploit prediction

39.59% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.