Dual DHCP DNS Server version 8.01 contains a critical DNS cache poisoning vulnerability that allows remote attackers to inject forged DNS responses due to insufficient validation of upstream DNS server origin. The flaw exists because the application matches responses primarily by transaction ID (TXID) without verifying that responses originate from legitimate configured upstream servers, enabling attackers to redirect victims to malicious destinations. The vulnerability carries a CVSS 3.1 score of 9.1 (CRITICAL) with a network-based attack vector requiring no privileges or user interaction, indicating high exploitability. The attack has high integrity and availability impacts, as successful exploitation enables DNS cache poisoning and potential service disruption, though confidentiality is not directly affected. There is currently no evidence of active exploitation in the wild, and the vulnerability does not appear on the CISA Known Exploited Vulnerabilities catalog. While the EPSS score of 0.00144 indicates lower probability of exploitation relative to other CVEs, organizations running Dual DHCP DNS Server 8.01 should prioritize patching given the critical severity rating and straightforward attack requirements.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
| N/A | N/A | n/aCNA affected |
CVSS version used by this source: 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
The average CVE in this peer group has 0.0 Twitter, 0.1 Reddit, 0.3 Bluesky, 0.3 Mastodon, and 2.4 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.3 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Remediation records are not available for this CVE.