CVE-2024-1975: SIG(0) can be used to exhaust CPU resources
If a server hosts a zone containing a “KEY” Resource Record, or a resolver DNSSEC-validates a “KEY” Resource Record from a DNSSEC-signed domain in cache, a client can exhaust resolver CPU resources by sending a stream of SIG(0) signed requests.
This vulnerability affects the following upstream's bind9 versions: 9.0.0 -> 9.11.37 9.16.0 -> 9.16.50 9.18.0 -> 9.18.27 9.19.0 -> 9.19.24
Other sources
If a server hosts a zone containing a "KEY" Resource Record, or a resolver DNSSEC-validates a "KEY" Resource Record from a DNSSEC-signed domain in cache, a client can exhaust resolver CPU resources by sending a stream of SIG(0) signed requests. This issue affects BIND 9 versions 9.0.0 through 9.11.37, 9.16.0 through 9.16.50, 9.18.0 through 9.18.27, 9.19.0 through 9.19.24, 9.9.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.49-S1, and 9.18.11-S1 through 9.18.27-S1.
— NVD
ISC BIND is vulnerable to a denial of service, caused by an error if a server hosts a zone containing a "KEY" Resource Record, or a resolver DNSSEC-validates a "KEY" Resource Record from a DNSSEC-signed domain in cache. By sending a stream of SIG(0) signed requests, a remote attacker could exploit this vulnerability to exhaust all available CPU resources.
— IBM
SIG(0) can be used to exhaust CPU resources
— Microsoft
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2024-1975?
CVE-2024-1975 has been classified with a significant severity due to its potential to exhaust resolver CPU resources.
How do I fix CVE-2024-1975?
To fix CVE-2024-1975, update BIND 9 to versions 1:9.16.50-1~deb11u2, 1:9.16.50-1~deb11u1, 1:9.18.28-1~deb12u2, or 1:9.20.4-4, or upgrade your F5 BIG-IP (DNS) to version 17.1.2 or above.
Which software is affected by CVE-2024-1975?
CVE-2024-1975 affects BIND 9 and F5 BIG-IP (DNS) in specified version ranges.
What types of attacks does CVE-2024-1975 facilitate?
CVE-2024-1975 facilitates denial-of-service attacks by exhausting CPU resources through SIG(0) signed requests.
Is a workaround available for CVE-2024-1975?
There is no mention of a specific workaround for CVE-2024-1975; upgrading to the patched versions is recommended.