Skip to content
Fencer Vulns
critical 9.8

CVE-1999-0199 json

manual/search.texi in the GNU C Library (aka glibc) before 2.2 lacks a statement about the unspecified tdelete return value upon deletion o…

published 2020-10-06 6 y ago modified 2026-09-25 44 d ago also EUVD-1999-0199

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

manual/search.texi in the GNU C Library (aka glibc) before 2.2 lacks a statement about the unspecified tdelete return value upon deletion of a tree's root, which might allow attackers to access a dangling pointer in an application whose developer was unaware of a documentation update from 1999.

Patch / fix

  • gnu glibc 2.2
  • glibc Debian 14, Debian 13, Debian 12 2.2-1

debian advisories DEBIAN-CVE-1999-0199

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-1999-0199 updated cvss 0.0

glibc: manual/search.texi lacks a statement about the unspecified tdelete return value upon deletion of a tree's root

  • Red Hat Enterprise Linux 5 glibc Red Hat Enterprise Linux 6 nscd, glibc, glibc-utils, glibc-common Red Hat Enterprise Linux 7 nscd, glibc, glibc-utils, glibc-common Red Hat Enterprise Linux 8 nscd, glibc, libnsl, nss_db, nss_hesiod, glibc-utils, +7 more
    not 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

2.40% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • cee.studio https://www.cee.studio/tdelete.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

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.