Security Advisory

CVE-2020-25684: dnsmasq DNSpooq Cache Poisoning

Last updated:
  • CVE-2020-25684

CVE-2020-25684 is a DNS cache-poisoning weakness in dnsmasq before 2.83: it does not tie each reply to the exact address and port of the forwarded query, so forged replies are easier to get accepted. NVD scores it 3.7. Part of DNSpooq, it affects every build, and Cisco, Juniper and OpenWrt name affected devices.

Vulnerability summary

CVSS base score

3.7

Low severity

EPSS score (FIRST)

4.2%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

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

Affected components

ComponentCPEVersion range
dnsmasq (DNS forwarding, forward.c reply_query)cpe:2.3:a:thekelleys:dnsmasq:*:*:*:*:*:*:*:*before 2.83, all build variants (dnsmasq CHANGELOG 2.83, OpenWrt advisory 2021-01-19-1)
Cisco access points, IR800 and CGR1000 routers, Wireless Gateway for LoRaWAN, Meraki MR and MS—per product, e.g. IR800 Guest OS fixed in 15.9(3)M4, LoRaWAN gateway in 2.1.0.3 (cisco-sa-dnsmasq-dns-2021-c5mrdf3g)
OpenWrt dnsmasq, dnsmasq-dhcpv6 and dnsmasq-full packages—OpenWrt 19.07.0 to 19.07.5; fixed in 19.07.6 (OpenWrt advisory 2021-01-19-1)

What does this mean for affected devices?

CVE-2020-25684 weakens how dnsmasq matches DNS replies to the queries it forwarded. NVD's description says dnsmasq checks in forward.c:reply_query() whether the reply's destination address and port belong to some pending query, but "does not use the address/port to retrieve the exact forwarded query". That substantially reduces the attempts an attacker needs to forge an accepted reply, contrary to RFC 5452. Chained with CVE-2020-25685 or CVE-2020-25686, the attack gets easier still. NVD 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, and its CPE also lists Arista EOS ranges (NVD).

The dnsmasq CHANGELOG entry for 2.83 describes the fix: only accept UDP replies "at the address from which the query was originated", which "keeps as much entropy in the {query-ID, random-port} tuple as possible, to help defeat cache poisoning attacks". The low base score covers a single flaw. The practical result of the three DNSpooq poisoning CVEs together is that every client using the device as its resolver can be sent to an attacker's address.

Unlike the DNSSEC overflows such as CVE-2020-25681, this CVE does not depend on build options. OpenWrt's advisory 2021-01-19-1 says CVE-2020-25684 and CVE-2020-25686 affect all three of its dnsmasq package variants. It lists OpenWrt 19.07.0 to 19.07.5 as affected and the fix in 19.07.6.

Vendors whose products were not hit by the overflows were hit by this one. Cisco's DNSpooq advisory, first published 2021-01-19 and final at version 1.4 on 2021-08-30, lists products susceptible to cache poisoning. They include Aironet 1560, 1810, 1815, 1830, 1850, 2800, 3800 and 4800 access points, Catalyst 9100 and IW6300 access points, the 1000 Series Connected Grid Routers (CGR1000 compute module), the IR800 Integrated Services Router guest OS (fixed in 15.9(3)M4), the Wireless Gateway for LoRaWAN (fixed in 2.1.0.3), and Meraki MR and MS. Cisco lists no workarounds. In CERT/CC VU#434904, Juniper reports Mist access points and the Wi-Fi Mini-PIM card for SRX branch devices affected through DNS, Check Point reports its SMB appliances vulnerable on internal LAN and Wi-Fi networks, and Cradlepoint rates these CVEs Low/Medium on NetCloud OS with default settings.

Exposure decides priority. An off-path attacker needs to make the device forward queries and then race forged replies, which is easiest from the LAN or when DNS is open on WAN. Our dnsmasq vulnerabilities in embedded firmware guide covers binding dnsmasq to LAN interfaces and closing port 53 on WAN. Our input handling fix guide covers validating untrusted protocol data as a class.

CVE-2020-25684 is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13), and FIRST EPSS gives it 0.0416, the 91st percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).

To fix it, upgrade to dnsmasq 2.83 or later, or install the vendor firmware listed above. The Debian Security Tracker shows backports such as 2.80-1+deb10u1 (DSA-4844-1). OpenWrt's interim mitigations are to disable caching (cachesize='0') and reduce dnsforwardmax to 50. CERT/CC also recommends stateful filtering that drops unsolicited DNS responses.

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • reply_query() does not use address/port to retrieve the exact forwarded query, contrary to RFC 5452; chains with CVE-2020-25685/-25686; NVD CVSS 3.1 3.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N); dnsmasq before 2.83; Arista EOS CPEs. — NVD
  • 2.83: only accept UDP replies at the address from which the query was originated, to keep query-ID/port entropy. — dnsmasq CHANGELOG
  • CVE-2020-25684 and -25686 affect all OpenWrt dnsmasq variants; 19.07.0-19.07.5 affected, fixed in 19.07.6; mitigations cachesize=0, dnsforwardmax=50. — OpenWrt Security Advisory 2021-01-19-1
  • Cisco products susceptible to cache poisoning: Aironet and Catalyst APs, CGR1000, IR800 (15.9(3)M4), LoRaWAN gateway (2.1.0.3), Meraki MR/MS; no workarounds; v1.4 final 2021-08-30. — Cisco Security Advisory cisco-sa-dnsmasq-dns-2021-c5mrdf3g
  • Juniper Mist APs and SRX Wi-Fi Mini-PIM affected via DNS; Check Point SMB vulnerable on LAN/Wi-Fi; Cradlepoint Low/Medium by default; stateful filtering of unsolicited DNS responses recommended. — CERT/CC VU#434904
  • Buster fixed in 2.80-1+deb10u1 (DSA-4844-1). — Debian Security Tracker
  • Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.0416 (91st percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. Cisco Security Advisory: DNSpooq vulnerabilities in dnsmasq
  3. CERT/CC VU#434904 (DNSpooq)
  4. OpenWrt Security Advisory 2021-01-19-1: dnsmasq multiple vulnerabilities
  5. dnsmasq CHANGELOG
  6. Debian Security Tracker
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Does CVE-2020-25684 need DNSSEC to be enabled?

No. It sits in the general DNS forwarding path, and OpenWrt reports that it affects all of its dnsmasq package variants, including the default one without DNSSEC (per OpenWrt and the dnsmasq CHANGELOG).

Which Cisco devices are affected by CVE-2020-25684?

Cisco lists Aironet and Catalyst access points, the CGR1000 compute module, the IR800 guest OS, the Wireless Gateway for LoRaWAN and Meraki MR and MS as susceptible to the DNSpooq cache-poisoning issues. No Cisco product was affected by the DNSSEC overflows (per Cisco).

Why is CVE-2020-25684 scored only 3.7?

NVD scores the flaw alone with high attack complexity and a low integrity impact. NVD notes that chaining it with CVE-2020-25685 or CVE-2020-25686 lowers the attack complexity, and dnsmasq 2.83 fixed all three together (per NVD and the dnsmasq CHANGELOG).

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

No, not as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0416, the 91st percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).