First published: Mon Feb 12 2024(Updated: )
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Microsoft Windows Server 2008 R2 | ||
Microsoft Windows Server 2022 | ||
Microsoft Windows Server 2012 R2 | ||
Microsoft Windows Server 2022 | ||
Microsoft Windows Server 2012 R2 | ||
Microsoft Windows Server 2019 | ||
Microsoft Windows Server 2008 R2 | ||
Microsoft Windows Server 2016 | ||
Microsoft Windows Server 2016 | ||
Microsoft Windows Server 2019 | ||
Microsoft Windows Server 2012 x64 | ||
Microsoft Windows Server 2012 x64 | ||
Microsoft Windows Server 2022 23H2 | ||
debian/bind9 | 1:9.16.50-1~deb11u2 1:9.16.50-1~deb11u3 1:9.18.28-1~deb12u2 1:9.18.33-1~deb12u2 1:9.20.4-4 1:9.20.5-1 | |
debian/dnsjava | <=2.1.8-2 | 3.6.2-2 |
debian/dnsmasq | <=2.85-1 | 2.85-1+deb11u1 2.90-4~deb12u1 2.91~test9-1 |
debian/knot-resolver | <=5.3.1-1+deb11u1 | 5.6.0-1+deb12u1 5.7.4-2 |
debian/pdns-recursor | <=4.4.2-3 | 4.8.8-1 4.8.8-1+deb12u1 5.1.3-2 5.2.0-2 |
debian/systemd | <=247.3-7+deb11u5 | 247.3-7+deb11u6 252.33-1~deb12u1 257.3-1 |
debian/unbound | 1.13.1-1+deb11u2 1.13.1-1+deb11u4 1.17.1-2+deb12u2 1.22.0-1 | |
F5 BIG-IP and BIG-IQ Centralized Management | >=17.1.0<=17.1.1 | 17.1.2 |
F5 BIG-IP and BIG-IQ Centralized Management | >=16.1.0<=16.1.5 | |
F5 BIG-IP and BIG-IQ Centralized Management | >=15.1.0<=15.1.10 | |
redhat/bind | <9.16.48 | 9.16.48 |
redhat/bind | <9.18.24 | 9.18.24 |
redhat/bind | <9.19.21 | 9.19.21 |
Red Hat Enterprise Linux | =6.0 | |
Red Hat Enterprise Linux | =7.0 | |
Red Hat Enterprise Linux | =8.0 | |
Red Hat Enterprise Linux | =9.0 | |
Microsoft Windows Server 2008 Itanium | =r2-sp1 | |
Microsoft Windows Server 2012 x64 | ||
Microsoft Windows Server 2012 x64 | =r2 | |
Microsoft Windows Server 2016 | ||
Microsoft Windows Server 2019 | ||
Microsoft Windows Server 2022 | ||
Microsoft Windows Server 2022 23H2 | ||
Fedora | =39 | |
dnsmasq | <2.90 | |
nic knot resolver | <5.71 | |
PowerDNS | >=4.8.0<4.8.6 | |
PowerDNS | >=4.9.0<4.9.3 | |
PowerDNS | >=5.0.0<5.0.2 | |
ISC BIND | >=9.0.0<=9.16.46 | |
ISC BIND | >=9.18.0<=9.18.22 | |
ISC BIND | >=9.19.0<=9.19.20 | |
libunbound | <1.19.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-50387 has been assessed with a severity level that allows remote attackers to cause a denial of service.
CVE-2023-50387 affects multiple versions of Microsoft Windows Server, various DNS software including BIND and PowerDNS, and several Linux distributions.
To fix CVE-2023-50387, apply the specific patches and updates provided by your software vendor.
The vulnerability in CVE-2023-50387 originates from certain DNSSEC aspects of the DNS protocol that can be exploited for denial of service.
While updating is highly recommended, temporary network configurations to limit DNS response processing might serve as a workaround for CVE-2023-50387.