Skip to main content

CVE-2025-30192: CWE-345 Insufficient Verification of Data Authenticity in PowerDNS Recursor

High
VulnerabilityCVE-2025-30192cvecve-2025-30192cwe-345
Published: Mon Jul 21 2025 (07/21/2025, 12:49:31 UTC)
Source: CVE Database V5
Vendor/Project: PowerDNS
Product: Recursor

Description

An attacker spoofing answers to ECS enabled requests sent out by the Recursor has a chance of success higher than non-ECS enabled queries. The updated version include various mitigations against spoofing attempts of ECS enabled queries by chaining ECS enabled requests and enforcing stricter validation of the received answers. The most strict mitigation done when the new setting outgoing.edns_subnet_harden (old style name edns-subnet-harden) is enabled.

AI-Powered Analysis

AILast updated: 07/21/2025, 13:16:25 UTC

Technical Analysis

CVE-2025-30192 is a high-severity vulnerability affecting the PowerDNS Recursor, a widely used DNS resolver software. The vulnerability stems from insufficient verification of data authenticity (CWE-345) specifically related to EDNS Client Subnet (ECS) enabled queries. ECS is a DNS extension that allows recursive resolvers to include part of the client's IP address in queries to authoritative servers, enabling geographically optimized responses. However, this feature also introduces complexity and potential attack vectors. In this case, an attacker can spoof DNS answers to ECS-enabled requests with a higher success probability than for non-ECS queries. This spoofing could lead to denial of service or manipulation of DNS responses, impacting availability. The vulnerability does not affect confidentiality or integrity directly but can cause significant disruption by providing incorrect DNS responses or causing service outages. The PowerDNS team has introduced mitigations in updated versions, including chaining ECS-enabled requests and enforcing stricter validation of received answers. The most stringent mitigation is available via the configuration setting outgoing.edns_subnet_harden (previously edns-subnet-harden), which hardens the validation process for ECS queries, reducing the risk of spoofing. The CVSS 3.1 score is 7.5 (high), reflecting the network attack vector, low attack complexity, no privileges or user interaction required, and an impact limited to availability. No known exploits are currently reported in the wild, but the vulnerability's nature and severity warrant prompt attention.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, especially for those relying on PowerDNS Recursor for DNS resolution in critical infrastructure, enterprise networks, or service provider environments. Spoofed DNS responses can lead to denial of service conditions, disrupting access to internal and external resources, potentially affecting business continuity. Although confidentiality and integrity are not directly compromised, availability degradation can cause operational downtime, impacting sectors such as finance, healthcare, telecommunications, and government services. Additionally, DNS is a foundational service; disruptions can cascade to other dependent applications and services. The increased spoofing success rate for ECS-enabled queries is particularly concerning for organizations leveraging ECS for geo-aware DNS routing, common in content delivery networks and cloud services prevalent in Europe. Given the high reliance on DNS and the critical role of PowerDNS in many European networks, this vulnerability poses a tangible risk to service reliability and trustworthiness.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Upgrade PowerDNS Recursor to the latest version that includes the ECS spoofing mitigations. Even though no patch links are provided, monitoring official PowerDNS channels for updates is critical. 2) Enable the outgoing.edns_subnet_harden setting to enforce the strictest validation of ECS-enabled queries, significantly reducing spoofing risk. 3) Review and audit DNS resolver configurations to ensure ECS is enabled only where necessary, minimizing the attack surface. 4) Implement network-level protections such as DNS response validation, DNSSEC validation where applicable, and rate limiting to detect and mitigate spoofed or anomalous DNS traffic. 5) Monitor DNS traffic logs for unusual patterns indicative of spoofing attempts or DNS anomalies. 6) Coordinate with upstream DNS providers and peers to ensure consistent ECS handling and validation. 7) Prepare incident response plans specific to DNS service disruptions to minimize downtime in case of exploitation. These measures go beyond generic advice by focusing on ECS-specific configurations and operational monitoring tailored to this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
OX
Date Reserved
2025-03-18T08:39:46.884Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 687e3a12a83201eaac0f8674

Added to database: 7/21/2025, 1:01:06 PM

Last enriched: 7/21/2025, 1:16:25 PM

Last updated: 7/21/2025, 1:16:25 PM

Views: 2

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats