CVE-2008-5277 json
PowerDNS before 2.9.21.2 allows remote attackers to cause a denial of service (daemon crash) via a CH HINFO query.
published 2008-12-09 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-5254
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.4%
- EPSS 3.4% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
PowerDNS before 2.9.21.2 allows remote attackers to cause a denial of service (daemon crash) via a CH HINFO query.
Patch / fix
- pdns Debian 14, Debian 13, Debian 12 2.9.21.2-1
debian advisories DEBIAN-CVE-2008-5277
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-2008-5277 updated
pdns: DoS (daemon crash) via a CH HINFO query.
-
Red Hat All currently supported Red Hat productsnot 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
3.38% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-16 Configuration
References
-
lists.opensuse.org
/opensuse-security-announce/2008-12/msg00002.html
vendor-advisory
-
security.gentoo.org
/glsa/glsa-200812-19.xml
vendor-advisory
- doc.powerdns.com /powerdns-advisory-2008-03.html
-
securitytracker.com
/id?1021304
vdb-entry
-
secunia.com
/advisories/33264
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/47076
vdb-entry
-
securityfocus.com
/bid/32627
vdb-entry
-
secunia.com
/advisories/32979
third-party-advisory
Sources
- CVE List CVE-2008-5277
- NVD CVE-2008-5277
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.