Security Advisory

CVE-2020-25685: dnsmasq DNSpooq Weak Reply Hash

Last updated:
  • CVE-2020-25685

CVE-2020-25685 is a DNS cache-poisoning weakness in dnsmasq before 2.83: it matched replies to forwarded queries using only a weak hash of the query name, CRC32 in builds without DNSSEC. Colliding names make forged replies easier to get accepted. NVD scores it 3.7, and Siemens, Cisco and Juniper name affected routers and access points.

Vulnerability summary

CVSS base score

3.7

Low severity

EPSS score (FIRST)

2.2%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2020-25685 · Source: NVD

Affected components

ComponentCPEVersion range
dnsmasq (DNS forwarding, forward.c reply_query)cpe:2.3:a:thekelleys:dnsmasq:*:*:*:*:*:*:*:*before 2.83; CRC32 in builds without DNSSEC, SHA-1 with DNSSEC (NVD, dnsmasq CHANGELOG 2.83)
Siemens RUGGEDCOM RM1224, SCALANCE M-800 and SCALANCE S615—fixed in V6.4 (Siemens ProductCERT SSA-646763)
Siemens SCALANCE SC-600—fixed in V2.1.3 (Siemens ProductCERT SSA-646763)
Siemens SCALANCE W1750Dcpe:2.3:o:siemens:scalance_w1750d_firmware:*:*:*:*:*:*:*:*no remediation available; mitigation only (Siemens ProductCERT SSA-646763)
Cisco access points, IR800 and CGR1000 routers, Wireless Gateway for LoRaWAN, Meraki MR and MS—per product (cisco-sa-dnsmasq-dns-2021-c5mrdf3g)

What does this mean for affected devices?

CVE-2020-25685 weakens how dnsmasq checks that a DNS reply answers the question it forwarded. NVD's description says forward.c:reply_query() identifies the matching query "by only using a weak hash of the query name". The hash is "CRC32 when dnsmasq is compiled without DNSSEC, SHA-1 when it is", so an off-path attacker can "find several different domains all having the same hash". That substantially reduces the attempts needed to forge an accepted reply, contrary to RFC 5452, and chaining it with CVE-2020-25684 lowers the attack complexity further. NVD records CWE-326 and scores it 3.7 (low), vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N, for dnsmasq before 2.83. Its CPE configuration also lists Arista EOS ranges (NVD).

The dnsmasq CHANGELOG for 2.83 replaced the check with SHA-256, describing the old hashes as "the slightly insecure SHA-1 (when compiled with DNSSEC) or the very insecure CRC32 (otherwise)". So the weakest case is the common embedded one, a build without DNSSEC. Red Hat makes the same point in CERT/CC VU#434904: RHEL 8 builds dnsmasq with DNSSEC, "thus SHA-1 is used as a hash for query names instead of CRC32, making collisions harder to find."

Siemens ProductCERT SSA-646763, first published 2021-01-19 and at V1.3 since 2021-05-11, lists CVE-2020-25685 for its industrial routers and access points. It describes the flaw as missing query-name (RRNAME) checks that "could allow a remote attacker to spoof DNS traffic that can lead to DNS cache poisoning", classifies it as CWE-290 and scores it 4.0:

  • RUGGEDCOM RM1224 and SCALANCE M-800: fixed in V6.4. Siemens notes that the DNS proxy is enabled by default on both.
  • SCALANCE S615: fixed in V6.4; DNS proxy disabled by default.
  • SCALANCE SC-600: fixed in V2.1.3; DNS proxy disabled by default.
  • SCALANCE W1750D: no remediation is available, and revision 1.3 of 2021-05-11 "clarified that a solution for SCALANCE W1750D is not expected". If OpenDNS, Captive Portal or URL redirection are unused, Siemens recommends blocking incoming access to port 53/UDP.

Siemens' workaround for the routers is to disable the DNS proxy and configure internal devices to use a different DNS server. Cisco's DNSpooq advisory, final at version 1.4 on 2021-08-30, lists products susceptible to the cache-poisoning CVEs. They include Aironet and Catalyst 9100 access points, the CGR1000 compute module, the IR800 guest OS (fixed in 15.9(3)M4), the Wireless Gateway for LoRaWAN (fixed in 2.1.0.3) and Meraki MR and MS. In the CERT/CC note, Juniper reports Mist access points and the SRX Wi-Fi Mini-PIM affected, and Check Point reports its SMB appliances vulnerable on LAN and Wi-Fi.

One source disagrees on scope. OpenWrt's advisory 2021-01-19-1 groups CVE-2020-25685 with the DNSSEC problems and says it affects only the dnsmasq-full package. The CHANGELOG and NVD both say builds without DNSSEC used CRC32, so we would not rely on that split for OpenWrt's default dnsmasq and dnsmasq-dhcpv6 packages before 19.07.6. Our dnsmasq vulnerabilities in embedded firmware guide treats this CVE the same way and covers binding dnsmasq to LAN interfaces and closing port 53 on WAN. The related DNSpooq pages are CVE-2020-25684 (address and port matching) and CVE-2020-25686 (repeated queries). For spoofing defences as a class, see our authentication bypass fix guide.

CVE-2020-25685 is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.0223, the 83rd percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).

To fix it, upgrade to dnsmasq 2.83 or later, or install the vendor firmware above. The Debian Security Tracker shows buster fixed in 2.80-1+deb10u1 (DSA-4844-1). Stretch was left unfixed as a minor issue, partly because its build "uses SHA-1 and not CRC32". CERT/CC recommends stateful firewalls or NAT that block unsolicited DNS responses, and disabling caching on embedded devices when an upstream caching resolver is available.

How to fix this class of issueThis advisory's weakness class is Authentication bypass. Our practical guide covers how to detect, fix, verify and disclose it: How to fix authentication bypass in embedded firmware.

Evidence

  • reply_query() matches replies using only a weak hash of the query name (CRC32 without DNSSEC, SHA-1 with); contrary to RFC 5452; chaining with CVE-2020-25684 reduces complexity; CWE-326; CVSS 3.1 3.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N); before 2.83; Arista EOS CPEs. — NVD
  • 2.83: SHA-256 replaces the slightly insecure SHA-1 (with DNSSEC) or very insecure CRC32 (otherwise). — dnsmasq CHANGELOG
  • Red Hat: RHEL 8 uses SHA-1 because it is built with DNSSEC; Juniper Mist APs and SRX Wi-Fi Mini-PIM affected; Check Point SMB vulnerable on LAN/Wi-Fi; best practice: block unsolicited DNS responses, disable caching on embedded devices. — CERT/CC VU#434904
  • RM1224, M-800, S615 fixed in V6.4; SC-600 in V2.1.3; W1750D no remediation (V1.3 2021-05-11: solution not expected); CWE-290; CVSS 4.0; DNS proxy on by default on M-800 and RM1224, off on S615 and SC-600. — Siemens ProductCERT SSA-646763
  • Products susceptible to DNSpooq cache poisoning: Aironet/Catalyst APs, CGR1000, IR800 (15.9(3)M4), LoRaWAN gateway (2.1.0.3), Meraki MR/MS; v1.4 final 2021-08-30. — Cisco Security Advisory cisco-sa-dnsmasq-dns-2021-c5mrdf3g
  • OpenWrt lists CVE-2020-25685 with the DNSSEC issues affecting only dnsmasq-full; 19.07.6 fixes all variants. — OpenWrt Security Advisory 2021-01-19-1
  • Buster fixed in 2.80-1+deb10u1 (DSA-4844-1); stretch ignored: minor issue, stretch uses SHA-1 and not CRC32. — Debian Security Tracker
  • Not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.0223 (83rd percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. Siemens ProductCERT SSA-646763: DNSpooq - Dnsmasq vulnerabilities in SCALANCE and RUGGEDCOM devices
  3. Cisco Security Advisory: DNSpooq vulnerabilities in dnsmasq
  4. CERT/CC VU#434904 (DNSpooq)
  5. OpenWrt Security Advisory 2021-01-19-1: dnsmasq multiple vulnerabilities
  6. dnsmasq CHANGELOG
  7. Debian Security Tracker
  8. CISA KEV
  9. FIRST EPSS

Frequently asked questions

Is CVE-2020-25685 worse with or without DNSSEC?

Without. dnsmasq before 2.83 used CRC32 to check replies when compiled without DNSSEC and SHA-1 when compiled with it; CRC32 collisions are far easier to find (per NVD and the dnsmasq CHANGELOG).

Which Siemens devices are affected by CVE-2020-25685?

RUGGEDCOM RM1224, SCALANCE M-800 and S615 (fixed in V6.4), SCALANCE SC-600 (fixed in V2.1.3) and SCALANCE W1750D, for which Siemens lists no remediation (per Siemens ProductCERT SSA-646763).

How do I reduce exposure to CVE-2020-25685 before upgrading?

Disable the DNS proxy or caching where an upstream resolver is available, keep port 53 closed on WAN, and block unsolicited DNS responses with a stateful firewall (per Siemens, CERT/CC and OpenWrt).

Is CVE-2020-25685 in the CISA KEV catalog?

No, not as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.0223, the 83rd percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).