CVE-2025-71058

DNS Cache Poisoning via Unvalidated UDP Responses

Published Apr 7, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
Dual DHCP DNS Server 8.01 improperly accepts and caches UDP DNS responses without validating that the response originates from a legitimate configured upstream DNS server. The implementation matches responses primarily by TXID and inserts results into the cache, enabling a remote attacker to inject forged responses and poison the DNS cache, potentially redirecting victims to attacker-controlled destinations.

Analysis

AI-generated

Technical impact

Dual DHCP DNS Server 8.01 accepts unsolicited UDP DNS responses without verifying that the answer comes from a legitimate upstream server. By matching solely the transaction identifier, the daemon inserts the data into its cache. If an attacker succeeds in delivering a forged reply, the stolen entries can resolve any queried domain name to an attacker‑controlled IP address, effectively redirecting network traffic to malicious destinations.

Affected Systems

The vulnerability is limited to the Dual DHCP DNS Server software version 8.01. No other vendors or product variants are referenced in the available data, so installations of this exact version are impacted.

Risk and Exploitability

With a CVSS score of 9.1 the flaw is considered high severity. The EPSS score of less than 1 % indicates a low likelihood of exploitation in the wild. It is not listed in the CISA Known Exploited Vulnerabilities catalog. The attack can be carried out from any network host that can reach the server’s DNS listening port, requiring no authentication or elevated privileges. Successful cache poisoning can compromise the confidentiality of traffic by redirecting users to malicious endpoints and can degrade availability by disrupting resolution of legitimate domain names.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest patch or upgrade Dual DHCP DNS Server to a version that validates upstream DNS responses
  • If an upgrade is not possible, configure firewall rules to block unsolicited DNS responses from untrusted sources
  • Activate any available strict upstream server validation features
  • Monitor DNS query and cache logs for anomalous domain entries and investigate any unexpected resolutions

Generated by OpenCVE AI on April 10, 2026 at 11:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title DNS Cache Poisoning via Unvalidated UDP Responses
Type Values Removed Values Added
Title Unvalidated DNS Responses Enable Cache Poisoning in Dual DHCP DNS Server 8.01
Weaknesses CWE-20
Type Values Removed Values Added
Weaknesses CWE-94
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Dual Dhcp Dns Server Project
Dual Dhcp Dns Server Project dual Dhcp Dns Server
Vendors & Products Dual Dhcp Dns Server Project
Dual Dhcp Dns Server Project dual Dhcp Dns Server
Type Values Removed Values Added
Title Unvalidated DNS Responses Enable Cache Poisoning in Dual DHCP DNS Server 8.01
Weaknesses CWE-20
Type Values Removed Values Added
Description Dual DHCP DNS Server 8.01 improperly accepts and caches UDP DNS responses without validating that the response originates from a legitimate configured upstream DNS server. The implementation matches responses primarily by TXID and inserts results into the cache, enabling a remote attacker to inject forged responses and poison the DNS cache, potentially redirecting victims to attacker-controlled destinations.
References
Weaknesses
  • CWE-94

    Improper Control of Generation of Code ('Code Injection')

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
May 14, 2026, 4:03 PM
Reserved
Jan 9, 2026, 12:00 AM
Status
Awaiting Analysis
Published
Apr 7, 2026, 7:16 PM
Modified
Jul 24, 2026, 10:10 PM