{"vulnerability": "CVE-2020-25685", "sightings": [{"uuid": "040626cd-73ef-4248-8221-340fb8089a58", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2020-25685", "type": "seen", "source": "https://www.kyberturvallisuuskeskus.fi/fi/dnspooq-haavoittuvuusjoukko-laajalti-kaytossa-olevassa-dnsmasq-ohjelmistossa", "content": "", "creation_timestamp": "2026-03-17T14:51:14.893301Z"}, {"uuid": "2bc2e253-a04f-4689-a142-6178a587916b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-25685", "type": "seen", "source": "https://t.me/VulnerabilityNews/19766", "content": "A flaw was found in dnsmasq before version 2.83. When getting a reply from a forwarded query, dnsmasq checks in the forward.c:reply_query() 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 reducing the number of attempts an attacker on the network would have to perform to forge a reply and get it accepted by dnsmasq. This issue contrasts with RFC5452, which specifies a query's attributes that all must be used to match a reply. This flaw allows an attacker to perform a DNS Cache Poisoning attack. If chained with CVE-2020-25685 or CVE-2020-25686, the attack complexity of a successful attack is reduced. The highest threat from this vulnerability is to data integrity.\nPublished at: January 20, 2021 at 05:15PM\nView on website", "creation_timestamp": "2021-01-20T18:46:29.000000Z"}, {"uuid": "8dbc65b4-ba79-4d60-81a8-277aa371dbe3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2020-25685", "type": "seen", "source": "https://www.kyberturvallisuuskeskus.fi/fi/dnspooq-haavoittuvuusjoukko-laajalti-kaytossa-olevassa-dnsmasq-ohjelmistossa", "content": "", "creation_timestamp": "2021-01-20T11:02:54.000000Z"}, {"uuid": "fc6c0874-f937-4f9d-8422-d0e6d836f3e9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-25685", "type": "seen", "source": "https://t.me/cibsecurity/22350", "content": "\u203c CVE-2020-25685 \u203c\n\nA flaw was found in dnsmasq before version 2.83. When getting a reply from a forwarded query, dnsmasq checks in forward.c:reply_query(), 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) this flaw allows an off-path attacker to find several different domains all having the same hash, substantially reducing the number of attempts they would have to perform to forge a reply and get it accepted by dnsmasq. This is in contrast with RFC5452, which specifies that the query name is one of the attributes of a query that must be used to match a reply. This flaw could be abused to perform a DNS Cache Poisoning attack. If chained with CVE-2020-25684 the attack complexity of a successful attack is reduced. The highest threat from this vulnerability is to data integrity.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-01-20T18:27:29.000000Z"}, {"uuid": "4c3c728a-34f2-4f28-8060-14fc11a074b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-25685", "type": "seen", "source": "https://t.me/CyberSecurityTechnologies/2534", "content": "#Whitepaper\n#Threat_Research\n\"DNSpooq: Cache Poisoning and RCE in Popular DNS Forwarder dnsmasq\", 2021.\n// CVE-2020-25684, CVE-2020-25685, \nCVE-2020-25686 - DNS-spoofing; CVE-2020-25681, CVE-2020-25682, CVE-2020-25683, CVE-2020-25687 - RCE.", "creation_timestamp": "2021-01-21T02:28:28.000000Z"}]}