CVE-2015-5230 json
The DNS packet parsing/generation code in PowerDNS (aka pdns) Authoritative Server 3.4.x before 3.4.6 allows remote attackers to cause a de…
published 2020-01-15 6 y ago modified 2026-06-17 4 mo ago also EUVD-2015-5226
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.0%
- EPSS 9.0% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
The DNS packet parsing/generation code in PowerDNS (aka pdns) Authoritative Server 3.4.x before 3.4.6 allows remote attackers to cause a denial of service (crash) via crafted query packets.
Patch / fix
- powerdns authoritative 3.4.6
- pdns Debian 14, Debian 13, Debian 12 3.4.6-1
debian advisories DEBIAN-CVE-2015-5230
- pdns openSUSE Tumbleweed 4.0.1-1.2
opensuse advisories openSUSE-SU-2024:10136-1
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-2015-5230 updated cvss 4.3
pdns: denial of service due to memory leak in exception handling routines
-
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
9.02% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- PowerDNS PowerDNS Authoritative Server
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
doc.powerdns.com
/md/security/powerdns-advisory-2015-02/
vendor-advisory
-
debian.org
/security/2015/dsa-3347
third-party-advisory
-
securitytracker.com
/id/1033475
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2015-5230
- NVD CVE-2015-5230
Fencer Intel 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.