Hello,
Today we have released PowerDNS Recursor 4.5.10, 4.6.3 and 4.7.2 due to a medium severity issue found. The security advisory only applies to Recursors running with protobuf logging enabled.
Please find the full text of the advisory below.
The changelogs are available at 4.5.10, 4.6.3, 4.7.2.
The source tarballs (4.5.10, 4.6.3, 4.7.2) and signatures (4.5.10, 4.6.3, 4.7.2) are available from our download server. Patches are available at patches. Packages for various distributions are available from our repository.
Note that PowerDNS Recursor 4.4.x and older releases are End of Life. Consult the EOL policy for more details.
PowerDNS Security Advisory 2022-02: incomplete exception handling related to protobuf message generation
|
1
2
3
4
5
6
7
8
9
|
CVE: CVE-2022-37428Date: 23th of August 2022.Affects: PowerDNS Recursor up to and including 4.5.9, 4.6.2 and 4.7.1Not affected: PowerDNS Recursor 4.5.10, 4.6.3 and 4.7.2Severity: MediumImpact: Denial of serviceExploit: This problem can be triggered by a remote attacker with access to the recursor if protobuf logging is enabledRisk of system compromise: NoneSolution: Upgrade to patched version, disable protobuf logging of responses |
This issue only affects recursors which have protobuf logging enabled using the
- protobufServer function with logResponses=true or
- outgoingProtobufServer function with logResponses=true
If either of these functions is used without specifying logResponses, its value is true.
An attacker needs to have access to the recursor, i.e. the remote IP must be in the access control list.
If an attacker queries a name that leads to an answer with specific properties, a protobuf message might be generated that causes an exception. The code does not handle this exception correctly, causing a denial of service.
