CVE-2008-2377 json
Use-after-free vulnerability in the _gnutls_handshake_hash_buffers_clear function in lib/gnutls_handshake.c in libgnutls in GnuTLS 2.3.5 th…
published 2008-08-08 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-2372
- cvss
- 7.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.5%
- EPSS 5.5% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
Use-after-free vulnerability in the _gnutls_handshake_hash_buffers_clear function in lib/gnutls_handshake.c in libgnutls in GnuTLS 2.3.5 through 2.4.0 allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via TLS transmission of data that is improperly used when the peer calls gnutls_handshake within a normal session, leading to attempted access to a deallocated libgcrypt handle.
Patch / fix
Exploit prediction
5.46% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- nabble.com http://www.nabble.com/Details-on-the-gnutls_handshake-local-crash-problem--GNUTLS-SA-2008-2--td18205022.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.6 | AV:N/AC:H/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
article.gmane.org
/gmane.comp.encryption.gpg.gnutls.devel/2947
mailing-list, patch
-
nabble.com
/Details-on-the-gnutls_handshake-local-crash-problem--GNUTLS-SA-2008-2--td18205022.html
mailing-list, exploit
- issues.rpath.com /browse/RPL-2650
- gnu.org /software/gnutls/security.html
-
vupen.com
/english/advisories/2008/2398
vdb-entry
-
securityfocus.com
/bid/30713
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44486
vdb-entry
-
secunia.com
/advisories/31505
third-party-advisory
Sources
- CVE List CVE-2008-2377
- NVD CVE-2008-2377
Fencer Vulns 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.