Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11411: CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data in NLnet Labs Unbound

0
Medium
VulnerabilityCVE-2025-11411cvecve-2025-11411cwe-349
Published: Wed Oct 22 2025 (10/22/2025, 12:28:02 UTC)
Source: CVE Database V5
Vendor/Project: NLnet Labs
Product: Unbound

Description

NLnet Labs Unbound up to and including version 1.24.1 is vulnerable to possible domain hijack attacks. Promiscuous NS RRSets that complement positive DNS replies in the authority section can be used to trick resolvers to update their delegation information for the zone. Usually these RRSets are used to update the resolver's knowledge of the zone's name servers. A malicious actor can exploit the possible poisonous effect by injecting NS RRSets (and possibly their respective address records) in a reply. This could be done for example by trying to spoof a packet or fragmentation attacks. Unbound would then proceed to update the NS RRSet data it already has since the new data has enough trust for it, i.e., in-zone data for the delegation point. Unbound 1.24.1 includes a fix that scrubs unsolicited NS RRSets (and their respective address records) from replies mitigating the possible poison effect. Unbound 1.24.2 includes an additional fix that scrubs unsolicited NS RRSets (and their respective address records) from YXDOMAIN and non-referral nodata replies, further mitigating the possible poison effect.

AI-Powered Analysis

AILast updated: 12/03/2025, 14:41:58 UTC

Technical Analysis

CVE-2025-11411 is a vulnerability classified under CWE-349, indicating acceptance of extraneous untrusted data alongside trusted data within the NLnet Labs Unbound DNS resolver up to version 1.24.2. The issue arises because Unbound processes NS RRSets found in the authority section of DNS responses, which are typically used to update the resolver's knowledge of zone delegation (i.e., the authoritative name servers for a domain). However, Unbound does not sufficiently validate whether these NS RRSets were solicited or trustworthy, allowing an attacker to inject malicious NS RRSets and associated address records. This injection can be performed through spoofed DNS packets or fragmentation attacks that evade standard validation. Once injected, Unbound updates its delegation information with attacker-controlled name servers, effectively enabling domain hijacking by redirecting DNS queries to malicious servers. This compromises the integrity of DNS resolution and can facilitate further attacks such as phishing, man-in-the-middle, or data interception. Unbound versions 1.24.1 and 1.24.2 introduced mitigations that scrub unsolicited NS RRSets from standard replies and from YXDOMAIN and non-referral nodata replies, respectively, reducing the attack surface. The vulnerability does not require authentication or user interaction but does require the attacker to be able to inject or spoof network packets to the resolver. The CVSS 4.0 score is 5.7 (medium severity), reflecting the moderate complexity of exploitation and significant impact on integrity but no direct impact on confidentiality or availability.

Potential Impact

For European organizations, this vulnerability poses a risk to the integrity of DNS resolution, which is foundational to internet and intranet operations. Successful exploitation can lead to domain hijacking, redirecting users and services to attacker-controlled infrastructure. This can facilitate credential theft, data interception, malware distribution, or disruption of critical services. Organizations in sectors such as finance, government, telecommunications, and critical infrastructure are particularly at risk due to the high value of their domains and services. Additionally, the attack can undermine trust in digital services and cause reputational damage. Since Unbound is widely used as a recursive DNS resolver in many European networks, especially in academic, governmental, and ISP environments, the scope of impact can be broad. The vulnerability could also be leveraged in targeted attacks against specific domains or regions, amplifying geopolitical risks. However, the absence of known exploits in the wild and the availability of patches reduce immediate risk if mitigations are applied promptly.

Mitigation Recommendations

European organizations should immediately verify their use of NLnet Labs Unbound and upgrade to version 1.24.2 or later, which includes fixes that scrub unsolicited NS RRSets from DNS replies. Network administrators should implement DNS response validation and monitoring to detect anomalous NS RRSet injections or unexpected delegation changes. Deploying DNSSEC validation where possible can provide an additional layer of protection by cryptographically verifying DNS data authenticity. Network-level protections such as ingress filtering (BCP 38) and anti-spoofing measures can reduce the risk of packet spoofing and fragmentation attacks used to exploit this vulnerability. Organizations should also audit DNS resolver configurations to ensure they do not accept or cache unsolicited authority data. Regularly reviewing DNS logs for suspicious delegation updates and employing anomaly detection tools can help identify exploitation attempts early. Collaboration with ISPs and upstream providers to enforce secure DNS practices is recommended. Finally, educating security teams about this specific threat and its indicators will improve incident response readiness.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
NLnet Labs
Date Reserved
2025-10-07T09:07:44.926Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68f8d2c779108345beab68dd

Added to database: 10/22/2025, 12:49:11 PM

Last enriched: 12/3/2025, 2:41:58 PM

Last updated: 12/8/2025, 3:24:50 AM

Views: 485

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

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