The nscd daemon in the GNU C Library (glibc) before version 2.5 does not close incoming client sockets if they cannot be handled by the dae…

published 2019-04-10 7 y ago modified 2026-06-16 4 mo ago also EUVD-2006-7231

cvss: 5.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

The nscd daemon in the GNU C Library (glibc) before version 2.5 does not close incoming client sockets if they cannot be handled by the daemon, allowing local users to carry out a denial of service attack on the daemon.

Patch / fix

fixed in 1 distros 1 links 1

gnu glibc 2.5

glibc Debian 14, Debian 13, Debian 12 2.5-1

debian advisories DEBIAN-CVE-2006-7254

sourceware.org/bugzilla/show_bug.cgi?id=2498 advisory

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-2006-7254 updated 2026-11-05 cvss 5.5

glibc: Not closing unhadleable client sockets due to nscd daemon leads to DoS.

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

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

CVSS scores

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

Classification

Weakness

CWE-19 Data Processing Errors

References

sourceware.org /bugzilla/show_bug.cgi?id=2498
issue-tracking, patch, third-party-advisory

Sources

CVE List CVE-2006-7254
NVD CVE-2006-7254

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.

Summary