CARVIEW |
Navigation
Previous topic
PowerDNS Security Advisory 2021-01: Specific query crashes Authoritative Server
Next topic
Contents
- PowerDNS Authoritative Nameserver
- Installing PowerDNS
- Upgrade Notes
- DNS Modes of Operation
- Migrating to PowerDNS
- Running and Operating
- Security of PowerDNS
- Performance and Tuning
- DNSSEC
- Per zone settings: Domain Metadata
- Dynamic DNS Update (RFC 2136)
- Catalog Zones (RFC 9432)
- TSIG
- Views
- Lua Records
- Guides and How Tos
- Backends
- Built-in Webserver and HTTP API
- Manual Pages
- Authoritative Server Settings
- Security Advisories
- PowerDNS Security Advisory 2022-01: incomplete validation of incoming IXFR transfer in Authoritative Server and Recursor
- PowerDNS Security Advisory 2021-01: Specific query crashes Authoritative Server
- PowerDNS Security Advisory 2020-06: Various issues in our GSS-TSIG support
- PowerDNS Security Advisory 2020-05: Leaking uninitialised memory through crafted zone records
- PowerDNS Security Advisory 2019-06: Denial of service via crafted zone records
- PowerDNS Security Advisory 2019-05: Denial of service via NOTIFY packets
- PowerDNS Security Advisory 2019-04: Denial of service via crafted zone records
- PowerDNS Security Advisory 2019-03: Insufficient validation in the HTTP remote backend
- PowerDNS Security Advisory 2018-05: Packet cache pollution via crafted query
- PowerDNS Security Advisory 2018-03: Crafted zone record can cause a denial of service
- PowerDNS Security Advisory 2018-02: Buffer overflow in dnsreplay
- PowerDNS Security Advisory 2017-04: Missing check on API operations
- PowerDNS Security Advisory 2016-05: Crafted zone record can cause a denial of service
- PowerDNS Security Advisory 2016-04: Insufficient validation of TSIG signatures
- PowerDNS Security Advisory 2016-03: Denial of service via the web server
- PowerDNS Security Advisory 2016-02: Crafted queries can cause abnormal CPU usage
- PowerDNS Security Advisory 2016-01: Crafted queries can cause unexpected backend load
- PowerDNS Security Advisory 2015-03: Packet parsing bug can lead to crashes
- PowerDNS Security Advisory 2015-02: Packet parsing bug can cause thread or process abortion
- PowerDNS Security Advisory 2015-01: Label decompression bug can cause crashes or CPU spikes
- PowerDNS Security Advisory 2012-01: PowerDNS Authoritative Server can be caused to generate a traffic loop
- PowerDNS Security Advisory 2008-03: Some PowerDNS Configurations can be forced to restart remotely
- PowerDNS Security Advisory 2008-02: By not responding to certain queries, domains become easier to spoof
- Older security advisories
- Changelogs
- End of life statements
- Frequently Asked Questions
- Backend writers’ guide
- Compiling PowerDNS
- Cryptographic software and export control
- Internals
- Supported Record Types
- PowerDNS/dnsdist license
This Page
- Docs
- Security Advisories
- PowerDNS Security Advisory 2022-01: incomplete validation of incoming IXFR transfer in Authoritative Server and Recursor
PowerDNS Security Advisory 2022-01: incomplete validation of incoming IXFR transfer in Authoritative Server and Recursor¶
- CVE: CVE-2022-27227
- Date: 25th of March 2022.
- Affects: PowerDNS Authoritative version 4.4.2, 4.5.3, 4.6.0 and PowerDNS Recursor 4.4.7, 4.5.7 and 4.6.0
- Not affected: PowerDNS Authoritative Server 4.4.3, 4.5.4, 4.6.1 and PowerDNS Recursor 4.4.8, 4.5.8 and 4.6.1
- Severity: Low
- Impact: Denial of service
- Exploit: This problem can be triggered by an attacker controlling the network path for IXFR transfers
- Risk of system compromise: None
- Solution: Upgrade to patched version, do not use IXFR in Authoritative Server
- In the Authoritative server this issue only applies to secondary zones for which IXFR transfers have been enabled and the network path to the primary server is not trusted. Note that IXFR transfers are not enabled by default.
- In the Recursor it applies to setups retrieving one or more RPZ zones from a remote server if the network path to the server is not trusted.
IXFR usually exchanges only the modifications between two versions of a zone, but sometimes needs to fall back to a full transfer of the current version. When IXFR falls back to a full zone transfer, an attacker in position of man-in-the-middle can cause the transfer to be prematurely interrupted. This interrupted transfer is mistakenly interpreted as a complete transfer, causing an incomplete zone to be processed. For the Authoritative Server, IXFR transfers are not enabled by default. The Recursor only uses IXFR for retrieving RPZ zones. An incomplete RPZ transfer results in missing policy entries, potentially causing some DNS names and IP addresses to not be properly intercepted.
We would like to thank Nicolas Dehaine and Dmitry Shabanov from ThreatSTOP for reporting and initial analysis of this issue.