First published: Fri Mar 29 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.
Affected Software | Affected Version | How to fix |
---|---|---|
F5 BIG-IP | >=17.1.0<=17.1.1 | 17.1.2 |
F5 BIG-IP | >=16.1.0<=16.1.5 | |
F5 BIG-IP | >=15.1.0<=15.1.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of F5-K000139092 is significant due to its potential to cause denial of service through excessive CPU consumption.
To fix F5-K000139092, upgrade your F5 BIG-IP system to a version that is not affected by the KeyTrap issue as specified in the advisory.
F5-K000139092 affects certain versions of F5 BIG-IP, specifically versions prior to 17.1.2, between 16.1.0 to 16.1.5, and between 15.1.0 to 15.1.10.
The 'KeyTrap' issue in F5-K000139092 refers to vulnerabilities in DNSSEC that allow remote attackers to exploit excessive CPU consumption through specific DNSSEC responses.
Organizations using affected versions of F5 BIG-IP that implement DNSSEC are at risk from F5-K000139092.