CVE-2012-1569

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 4%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

The asn1_get_length_der function in decoding.c in GNU Libtasn1 before 2.12, as used in GnuTLS before 3.0.16 and other products, does not properly handle certain large length values, which allows remote attackers to cause a denial of service (heap memory corruption and application crash) or possibly have unspecified other impact via a crafted ASN.1 structure.

CVSS v3
—
EG Score
0.0(none)
EPSS
90.3%
KEV
Not listed

Published

March 26, 2012

Last Modified

April 29, 2026

References (66)

Vendor Advisories for CVE-2012-1569(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibtasn1-3 (1.1-1ubuntu0.1) @ hardy2026-05-29ubuntu
redhatrhev-hypervisor6-0:6.2-20120423.1.el6_22012-04-30redhat
redhatgnutls-0:1.4.1-7.el5_8.22012-03-27redhat
redhatlibtasn1-0:2.3-3.el6_2.12012-03-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:23 UTCEPSS rescore
  2. 2026-07-06 02:19 UTCEPSS rescore
  3. 2026-07-06 02:19 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-04 06:27 UTCEPSS rescore
  6. 2026-07-02 14:01 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-29 14:02 UTCEPSS rescore
  11. 2026-06-28 14:03 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-27 03:05 UTCEPSS rescore
  15. 2026-06-27 03:05 UTCEPSS rescore
  16. 2026-06-25 13:46 UTCEPSS rescore
  17. 2026-06-25 13:46 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-21 14:53 UTCEPSS rescore
  22. 2026-06-21 01:56 UTCEPSS rescore
  23. 2026-06-21 01:56 UTCEPSS rescore
  24. 2026-06-19 19:22 UTCEPSS rescore
  25. 2026-06-19 19:22 UTCEPSS rescore
Show 50 more
  1. 2026-06-18 17:49 UTCEPSS rescore
  2. 2026-06-18 17:49 UTCEPSS rescore
  3. 2026-06-17 17:49 UTCEPSS rescore
  4. 2026-06-17 17:49 UTCEPSS rescore
  5. 2026-06-16 17:49 UTCEPSS rescore
  6. 2026-06-16 17:49 UTCEPSS rescore
  7. 2026-06-15 17:44 UTCEPSS rescore
  8. 2026-06-14 23:14 UTCEPSS rescore
  9. 2026-06-14 23:14 UTCEPSS rescore
  10. 2026-06-13 22:57 UTCEPSS rescore
  11. 2026-06-12 23:08 UTCEPSS rescore
  12. 2026-06-11 13:56 UTCEPSS rescore
  13. 2026-06-10 22:14 UTCEPSS rescore
  14. 2026-06-10 13:18 UTCEPSS rescore
  15. 2026-06-08 14:14 UTCEPSS rescore
  16. 2026-06-08 14:14 UTCEPSS rescore
  17. 2026-06-07 15:22 UTCEPSS rescore
  18. 2026-06-07 15:22 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-05 06:08 UTCEPSS rescore
  23. 2026-06-04 13:09 UTCEPSS rescore
  24. 2026-06-02 20:10 UTCEPSS rescore
  25. 2026-06-02 20:10 UTCEPSS rescore
  26. 2026-05-31 22:28 UTCEPSS rescore
  27. 2026-05-31 22:28 UTCEPSS rescore
  28. 2026-05-31 00:14 UTCEPSS rescore
  29. 2026-05-31 00:14 UTCEPSS rescore
  30. 2026-05-29 13:41 UTCEPSS rescore
  31. 2026-05-29 05:01 UTCEG score recompute
  32. 2026-05-29 05:01 UTCVendor advisory
  33. 2026-05-29 05:01 UTCGHSA enrichment
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-24 16:43 UTCEPSS rescore
  39. 2026-05-22 21:15 UTCEPSS rescore
  40. 2026-05-22 21:15 UTCEPSS rescore
  41. 2026-05-22 21:15 UTCEPSS rescore
  42. 2026-05-21 22:39 UTCEPSS rescore
  43. 2026-05-20 22:37 UTCEPSS rescore
  44. 2026-05-20 22:37 UTCEPSS rescore
  45. 2026-05-20 22:37 UTCEPSS rescore
  46. 2026-05-20 11:21 UTCEPSS rescore
  47. 2026-05-20 11:21 UTCEPSS rescore
  48. 2026-05-20 11:21 UTCEPSS rescore
  49. 2026-05-18 21:29 UTCEPSS rescore
  50. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2012-1569?
CVE-2012-1569 is a none vulnerability published on March 26, 2012. The asn1getlength_der function in decoding.c in GNU Libtasn1 before 2.12, as used in GnuTLS before 3.0.16 and other products, does not properly handle certain large length values, which allows remote attackers to cause a denial of service (heap memory corruption and application crash) or possibly…
When was CVE-2012-1569 disclosed?
CVE-2012-1569 was first published in the National Vulnerability Database on March 26, 2012, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2012-1569 actively exploited?
CVE-2012-1569 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2012-1569?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-1569, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2012-1569

Explore →

Is Your Infrastructure Affected by CVE-2012-1569?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs