DNS vulnerabilities

The KeyTrap vulnerability in the DNSSEC protocol allows a remote attacker to cause a Denial of Service (DoS) by sending DNSSEC responses containing many DNSKEY and RRSIG records. This leads to excessive CPU consumption on the DNS server, potentially causing overload.

A TSIG packet with name compression can crash DNS. Incorrect size calculations when a TSIG record contains compressed names lead to a large out-of-bounds write, causing a server crash.

A DNS issue occurs when the authoritative server responds very slowly and records expire in the meantime. In this case, TTL capping is not enforced due to lack of data. This does not happen during normal resolution.

An attacker can trigger an assertion failure by requesting crafted DNS records, waiting for them to be inserted into the records cache, then sending a query with qtype set to ANY.

A denial-of-service issue in the DNS implementation could cause an infinite loop. This may lead to a hang or unavailability of the service.

A lack of input validation allows for out-of-bounds reads caused by malicious or malformed packets. This may lead to data disclosure or a crash.

A malicious or malformed DNS packet without a payload can cause an out-of-bounds read, resulting in a crash (denial of service) or an incorrect computation. The vulnerability affects DNS packet processing.

The vulnerability in DNS allows remote attackers to use DNS name servers as traffic amplifiers. An attacker can send a UDP DNS query with a spoofed source address, resulting in more traffic to the victim than was sent by the attacker.