Skip to content
Fencer Intel
high 7.5

CVE-2012-2131 in the critical feed json

Multiple integer signedness errors in crypto/buffer/buffer.c in OpenSSL 0.9.8v allow remote attackers to conduct buffer overflow attacks, a…

published 2012-04-24 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2131

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
16.8%
EPSS 16.8% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

Multiple integer signedness errors in crypto/buffer/buffer.c in OpenSSL 0.9.8v allow remote attackers to conduct buffer overflow attacks, and cause a denial of service (memory corruption) or possibly have unspecified other impact, via crafted DER data, as demonstrated by an X.509 certificate or an RSA public key. NOTE: this vulnerability exists because of an incomplete fix for CVE-2012-2110.

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-2131 updated cvss 6.8

openssl: incomplete fix of CVE-2012-2110 for 0.9.x

  • Red Hat Enterprise Linux 4 openssl, openssl096b 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 (EDB-18756)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-18756 OpenSSL - ASN1 BIO Memory Corruption dos, 2012-04-19

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/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.