DNS cache poisoning via loose reply matching
Published Jan 20, 2021 · Updated Nov 4, 2025
DNS cache poisoning in dnsmasq before 2.83 allows remote attackers to redirect DNS clients through forged replies accepted by the forwarder. The forward.c reply_query() path checks whether an address and port belong to any pending query but does not bind them to the exact query being answered. Exploitation requires flooding forged UDP replies while a forwarded query is pending; a successful forgery inserts attacker-chosen DNS data into the cache.
Summary
What happened
DNS cache poisoning in dnsmasq before 2.83 allows remote attackers to redirect DNS clients through forged replies accepted by the forwarder. The forward.c reply_query() path checks whether an address and port belong to any pending query but does not bind them to the exact query being answered. Exploitation requires flooding forged UDP replies while a forwarded query is pending; a successful forgery inserts attacker-chosen DNS data into the cache.
The record
- CVE
- CVE-2020-25684
- Published
- Jan 20, 2021
- Updated
- Nov 4, 2025
- Vendor
- Simon Kelley
- Product
- dnsmasq
- Classifications
- CWE-358, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2021CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=dnsmasq 2.83
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo