Vulnerability of reply_query() function (forward.c): The Dnsmasq DNS server has vulnerabilities related to errors in implementing security checks for standard elements. This allows attackers to compromise the integrity of protected information.

The vulnerability of the replyquery function forward.c: The Dnsmasq DNS server is vulnerable due to the use of a weak hash. Exploiting this vulnerability could allow an attacker to compromise the integrity of the protected information...

Vulnerability of reply_query() function (forward.c): The Dnsmasq DNS server has vulnerabilities related to errors in implementing security checks for standard elements, allowing attackers to compromise the integrity of protected information.

The vulnerability of the replyquery function forward.c: The Dnsmasq DNS server has vulnerabilities related to errors in the implementation of security checks for standard elements. Exploiting this vulnerability could allow a malicious actor to compromise the integrity of the protected information...

DNS Cache Poisoning

apport is vulnerable to DNS cache poisoning. When getting a reply from a forwarded query, dnsmasq checks in forward.c:replyquery if the reply destination address/port is one of those used by the pending forwarded queries. However, it does not use the address/port to retrieve the exact forwarded...

dnsmasq: loose address/port check in reply_query() makes forging replies easier for an off-path attacker

A flaw was found in dnsmasq. When getting a reply from a forwarded query, dnsmasq checks in the forward.c:replyquery if the reply destination address/port is used by the pending forwarded queries. However, it does not use the address/port to retrieve the exact forwarded query, substantially...

dnsmasq: loose query name check in reply_query() makes forging replies easier for an off-path attacker

A flaw was found in dnsmasq. When getting a reply from a forwarded query, dnsmasq checks in forward.c:replyquery, which is the forwarded query that matches the reply, by only using a weak hash of the query name. Due to the weak hash CRC32 when dnsmasq is compiled without DNSSEC, SHA-1 when it is...

dnsmasq: loose query name check in reply_query() makes forging replies easier for an off-path attacker

A flaw was found in dnsmasq. When getting a reply from a forwarded query, dnsmasq checks in forward.c:replyquery, which is the forwarded query that matches the reply, by only using a weak hash of the query name. Due to the weak hash CRC32 when dnsmasq is compiled without DNSSEC, SHA-1 when it is...