Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2012-1573

gnutls: TLS record handling issue (GNUTLS-SA-2012-2, MU-201202-01)

Overview

Published
26 Mar 2012
Modified
29 Apr 2026
Medium CVE
0 Registry packages
14 OS packages
4 Linux distributions
Yes Fix available

Description

gnutls_cipher.c in libgnutls in GnuTLS before 2.12.17 and 3.x before 3.0.15 does not properly handle data encrypted with a block cipher, which allows remote attackers to cause a denial of service (heap memory corruption and application crash) via a crafted record, as demonstrated by a crafted GenericBlockCipher structure.

Source: OX vulnerability database

Severity

5 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

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

Weakness: CWE-310

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

debian 4 releases · 1 package

fixed 4
gnutls28
debian fixes for CVE-2012-1573
ReleasePackageFixed in
11 gnutls28 3.0.17-2
12 gnutls28 3.0.17-2
13 gnutls28 3.0.17-2
14 gnutls28 3.0.17-2

echo 1 release · 1 package

fixed 1
gnutls28
echo fixes for CVE-2012-1573
ReleasePackageFixed in
gnutls28 3.0.17-2

openSUSE 1 release · 1 package

fixed 1
gnutls
openSUSE fixes for CVE-2012-1573
ReleasePackageFixed inAdvisory
Tumbleweed gnutls +11 3.4.15-1.1 openSUSE-SU-2024:10105-1

root.io debian 2 releases · 1 package

fixed 2
rootio-gnutls28
root.io debian fixes for CVE-2012-1573
ReleasePackageFixed in
12 rootio-gnutls28 3.0.17-2
13 rootio-gnutls28 3.0.17-2

References

Show all 34 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.