CVE-2008-1447

NameCVE-2008-1447
DescriptionThe DNS protocol, as implemented in (1) BIND 8 and 9 before 9.5.0-P1, 9.4.2-P1, and 9.3.5-P1; (2) Microsoft DNS in Windows 2000 SP4, XP SP2 and SP3, and Server 2003 SP1 and SP2; and other implementations allow remote attackers to spoof DNS traffic via a birthday attack that uses in-bailiwick referrals to conduct cache poisoning against recursive resolvers, related to insufficient randomness of DNS transaction IDs and source ports, aka "DNS Insufficient Socket Entropy Vulnerability" or "the Kaminsky bug."
SourceCVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
ReferencesDSA-1603-1, DSA-1604-1, DSA-1605-1, DSA-1617-1, DSA-1619-1, DSA-1623-1, DTSA-147-1
Debian Bugs490123, 490217, 492465, 492698, 492700, 493599, 502275

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
adns (PTS)jessie, stretch1.5.0~rc1-1fixed
buster1.5.0~rc1-1.1fixed
bullseye, bookworm1.6.0-2fixed
sid, trixie1.6.1-1fixed
bind9 (PTS)jessie, jessie (lts)1:9.9.5.dfsg-9+deb8u31fixed
stretch (security)1:9.10.3.dfsg.P4-12.3+deb9u12fixed
stretch (lts), stretch1:9.10.3.dfsg.P4-12.3+deb9u16fixed
buster, buster (lts)1:9.11.5.P4+dfsg-5.1+deb10u13fixed
buster (security)1:9.11.5.P4+dfsg-5.1+deb10u11fixed
bullseye1:9.16.50-1~deb11u2fixed
bullseye (security)1:9.16.50-1~deb11u1fixed
bookworm (security), bookworm1:9.18.28-1~deb12u2fixed
sid, trixie1:9.20.2-1fixed
dnsmasq (PTS)jessie, jessie (lts)2.72-3+deb8u7fixed
stretch (security)2.76-5+deb9u3fixed
stretch (lts), stretch2.76-5+deb9u4fixed
buster, buster (lts)2.80-1+deb10u2fixed
buster (security)2.80-1+deb10u1fixed
bullseye2.85-1fixed
bookworm2.89-1fixed
sid, trixie2.90-4fixed
dnspython (PTS)jessie1.12.0-1fixed
stretch1.15.0-1+deb9u1fixed
buster1.16.0-1+deb10u1fixed
bullseye2.0.0-1fixed
bookworm2.3.0-1fixed
sid, trixie2.6.1-1fixed
libnet-dns-perl (PTS)jessie, jessie (lts)0.81-2+deb8u1fixed
stretch1.07-1fixed
buster1.19-1fixed
bullseye1.29-1fixed
bookworm1.36-1fixed
sid, trixie1.47-1fixed
pdnsd (PTS)jessie1.2.9a-par-2fixed
python-dns (PTS)jessie, stretch2.3.6-3fixed
buster2.3.6-4fixed
refpolicy (PTS)stretch2:2.20161023.1-9fixed
buster2:2.20190201-2fixed
bullseye2:2.20210203-7fixed
bookworm2:2.20221101-9fixed
sid, trixie2:2.20241013-1fixed
udns (PTS)jessie, buster, bullseye, stretch, bookworm0.4-1fixed
sid, trixie0.6-1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
adnssource(unstable)1.4-2unimportant492698
bind9sourceetch1:9.3.4-2etch3DSA-1603-1
bind9sourcelenny1:9.4.2-10+lenny1DTSA-147-1
bind9source(unstable)1:9.5.0.dfsg-5high
dnsmasqsourceetch2.35-1+etch4DSA-1623-1
dnsmasqsource(unstable)2.43-1medium490123
dnspythonsource(unstable)1.7.1-1unimportant492465
libnet-dns-perlsource(unstable)0.63-2low492700
pdnsdsource(unstable)1.2.6-par-11502275
python-dnssourceetch2.3.0-5.2+etch1DSA-1619-1
python-dnssource(unstable)2.3.1-5low490217
refpolicysourceetch0.0.20061018-5.1+etch1DSA-1617-1
refpolicysource(unstable)2:0.0.20080702-1
ruby1.9source(unstable)1.9.0.2-6low
udnssource(unstable)0.2-1493599

Notes

glibc stub resolver relies on source port randomisation in kernel
Just a stub resolver Linux kernel provides source port randomisation
adns is not suitable to use with untrusted responses, documented in README.Debian
Source port randomization from Lenny kernel should provide sufficient protection
since this is just a Perl nodule for DNS queries and not a high-profile server app like
Bind, it's unlikely that a home-grown fix will provide an implementation of higher
cryptographical quality. Marking the version from Lenny as fixed, since Lenny includes
a kernel which provides source port randomization
Unbound, djbdns, pdnsd and PowerDNS are affected by the underlying protocol issue, but
already use source port randomization.
Marking non-caching stub resolvers as low since these really should be fixed,
but are much less vulnerable than a caching server.

Search for package or bug name: Reporting problems