CVE-2012-0390 json
The DTLS implementation in GnuTLS 3.0.10 and earlier executes certain error-handling code only if there is a specific relationship between…
published 2012-01-06 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-0426
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
The DTLS implementation in GnuTLS 3.0.10 and earlier executes certain error-handling code only if there is a specific relationship between a padding length and the ciphertext size, which makes it easier for remote attackers to recover partial plaintext via a timing side-channel attack, a related issue to CVE-2011-4108.
Patch / fix
- gnutls28 Debian 14, Debian 13, Debian 12 3.0.11-1
debian advisories DEBIAN-CVE-2012-0390
- gnutls openSUSE Tumbleweed 3.4.15-1.1
opensuse advisories openSUSE-SU-2024:10105-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-0390 updated cvss 5.0
gnutls: DTLS plaintext recovery attack
-
Red Hat Enterprise Linux 4 gnutls Red Hat Enterprise Linux 5 gnutls Red Hat Enterprise Linux 6 gnutls, gnutls-guile, gnutls-utilsnot 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
Exploit prediction
1.13% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
lists.opensuse.org
/opensuse-security-announce/2014-03/msg00001.html
vendor-advisory
-
secunia.com
/advisories/57260
third-party-advisory
- isg.rhul.ac.uk /~kp/dtls.pdf
Sources
- CVE List CVE-2012-0390
- NVD CVE-2012-0390
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.