LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25686: A flaw was found in dnsmasq before version 2.83.

A flaw was found in dnsmasq before version 2.83. When receiving a query, dnsmasq does not check for an existing pending request for the same name and forwards a new request. By default, a maximum of 150 pending queries can be sent to upstream servers, so there can be at most 150 queries for the same name. This flaw allows an off-path attacker on the network to substantially reduce the number of attempts that it would have to perform to forge a reply and have it accepted by dnsmasq. This issue is mentioned in the "Birthday Attacks" section of RFC5452. 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Dnsmasq could accept a forged DNS reply more easily because it forwarded duplicate pending queries for the same name. A successful attack could poison DNS answers and redirect users or systems to attacker-controlled destinations. The source material does not show confirmed active exploitation.

Executive priority

Prioritize remediation on DNS infrastructure, edge appliances, routers, and embedded devices because poisoned DNS can redirect business traffic silently. Treat internet-adjacent or broadly reachable DNS forwarders as higher urgency.

Technical view

Before dnsmasq 2.83, duplicate pending queries for the same name were not checked before forwarding. Up to 150 similar pending upstream queries could exist, enabling an off-path network attacker to reduce DNS reply-forgery effort. Chaining with CVE-2020-25684 further reduces attack complexity.

Likely exposure

Exposure is likely where dnsmasq before 2.83 is used as a DNS forwarder or cache, including Linux distributions and embedded or network products that bundle dnsmasq. Confirm product-specific status through vendor advisories.

Exploitation context

The described attacker is off-path but on the network. The impact is DNS cache poisoning or forged DNS responses, primarily affecting data integrity. CISA KEV status is false in the supplied bundle, so active exploitation is not established here.

Researcher notes

This is a DNS transaction entropy weakness aligned with RFC5452 birthday-attack concerns. The bundle provides no exploit code, no CVSS vector, and no proof of active exploitation. Analysis should focus on dnsmasq versioning, vendor backports, and whether CVE-2020-25684 is also present.

Mitigation direction

  • Upgrade dnsmasq to 2.83 or a vendor-fixed package.
  • Apply relevant Debian, Fedora, Gentoo, or product vendor advisories.
  • Identify appliances or embedded systems that bundle dnsmasq.
  • Restrict DNS forwarding service exposure to trusted networks where feasible.
  • Review vendor guidance for any product-specific compensating controls.

Validation and detection

  • Inventory systems and products running dnsmasq.
  • Confirm installed dnsmasq versions are not before 2.83.
  • Check vendor advisories for distribution-specific fixed package versions.
  • Verify DNS forwarders are not exposed beyond intended networks.
  • Track CVE-2020-25684 because chaining reduces attack complexity.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-358: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-25686 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/adnsmasqdnsmasq 2.83Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.