Skip to content
WatchlistHigh

CVE-2012-2110Openssl Memory Corruption

The asn1_d2i_read_bio function in crypto/asn1/a_d2i_fp.c in OpenSSL before 0.9.8v, 1.0.0 before 1.0.0i, and 1.0.1 before 1.0.1a does not properly interpret integer data, which allows remote attackers to conduct buffer overflow attacks, and cause a denial of service (memory…

Published Apr 19, 2012 · Updated Aug 4, 2026 · Also known as DEBIAN-CVE-2012-2110

Key Facts

Patch immediately
  • CVE-2012-2110 is a high-severity vulnerability (CVSS 7.5 v2) affecting Openssl, rootio-openssl, openssl098e (amazon) and 22 more products.
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 48% probability of exploitation in the next 30 days.
  • Fixed versions are available, including compat-openssl097g 0.9.7g-146.22.1, compat-openssl097g-32bit 0.9.7g-146.22.1, libopenssl-1_1-devel 1.1.1l-1.2.
  • Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Scores

CVSS v2

7.5

AV:N/AC:L/Au:N/C:P/I:P/A:P

EPSS (30-day exploit likelihood)

48%

Higher than 98.8% of all scored CVEs

Exploit maturity

Proof of concept

ATLAS score

46/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

1

Proof-of-concept links

In-the-wild evidence

1

Reports of active use

Description

The asn1_d2i_read_bio function in crypto/asn1/a_d2i_fp.c in OpenSSL before 0.9.8v, 1.0.0 before 1.0.0i, and 1.0.1 before 1.0.1a does not properly interpret integer data, which allows 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.

Affected Products

161 affected entries in total
ProductAffected versionsFixed in
OpensslOpenssl0.9.1c, 0.9.2b, 0.9.3, 0.9.3a, 0.9.4, 0.9.5, 0.9.5a, 0.9.5a-beta10.9.8u
rootio-opensslrootioSee advisory1.0.1a-1
openssl098eamazonSee advisory0.9.8e-17.8.amzn1
openssl-develamazonSee advisory1.0.0i-1.41.amzn1
openssl-perlamazonSee advisory1.0.0i-1.41.amzn1
20 more affected products in the full CVE brief

Patched Releases

compat-openssl097g

0.9.7g-146.22.1

compat-openssl097g-32bit

0.9.7g-146.22.1

libopenssl-1_1-devel

1.1.1l-1.2

libopenssl-1_1-devel-32bit

1.1.1l-1.2

libopenssl-devel

0.9.8j-0.66.1, 1.0.2j-2.2

libopenssl-devel-32bit

1.0.2j-2.2

libopenssl0_9_8

0.9.8j-0.66.1

libopenssl0_9_8-32bit

0.9.8j-0.66.1

libopenssl0_9_8-hmac

0.9.8j-0.66.1

libopenssl0_9_8-hmac-32bit

0.9.8j-0.66.1

libopenssl1_0_0

1.0.2j-2.2

libopenssl1_0_0-32bit

1.0.2j-2.2

libopenssl1_0_0-hmac

1.0.2j-2.2

libopenssl1_0_0-hmac-32bit

1.0.2j-2.2

libopenssl1_0_0-steam

1.0.2h-4.1

libopenssl1_0_0-steam-32bit

1.0.2h-4.1

libopenssl1_1

1.1.1l-1.2

libopenssl1_1-32bit

1.1.1l-1.2

libopenssl1_1-hmac

1.1.1l-1.2

Openssl

0:0.9.7a-33.28, 0:0.9.7a-43.20.el4, 0:0.9.8e-7.el5_3.2, 0:1.0.0-4.el6_0.3, 0.9.8e-22.el5_8.3, 0.9.8j-0.66.1, 0.9.8o-4squeeze11, 1.0.0-20.el6_2.4, 1.0.0i-1.41.amzn1, 1.0.1a-1, 1.0.2j-2.2, 0.9.8u

openssl-1_1

1.1.1l-1.2

openssl-1_1-doc

1.1.1l-1.2

openssl-devel

0.9.8e-22.el5_8.3, 1.0.0-20.el6_2.4, 1.0.0i-1.41.amzn1

openssl-doc

0.9.8j-0.66.1, 1.0.2j-2.2

openssl-perl

0.9.8e-22.el5_8.3, 1.0.0-20.el6_2.4, 1.0.0i-1.41.amzn1

Timeline

  1. Publicly disclosed

    Apr 19, 2012

  2. Last updated

    Aug 4, 2026

Weakness Type

  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
  • CWE-681 Incorrect Conversion between Numeric Types

References

15 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2012-2110 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.