CVE-2025-2962

| EUVD-2025-19001 HIGH
2025-06-24 [email protected]
7.5
CVSS 3.1
Share

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
EUVD ID Assigned
Mar 15, 2026 - 22:36 euvd
EUVD-2025-19001
Analysis Generated
Mar 15, 2026 - 22:36 vuln.today
PoC Detected
Oct 30, 2025 - 15:50 vuln.today
Public exploit code
CVE Published
Jun 24, 2025 - 06:15 nvd
HIGH 7.5

Description

A denial-of-service issue in the dns implemenation could cause an infinite loop.

Analysis

CVE-2025-2962 is a denial-of-service vulnerability in a DNS implementation that triggers an infinite loop condition, allowing unauthenticated remote attackers to crash DNS services with high availability impact. The vulnerability affects DNS resolver implementations and has a CVSS score of 7.5 (High) with a network-based attack vector requiring no privileges or user interaction. While the CVE ID and basic metadata are provided, specific product names, versions, KEV status, EPSS scores, and public proof-of-concept availability cannot be confirmed from the limited data supplied.

Technical Context

The vulnerability exists in DNS protocol implementation logic, classified under CWE-835 (Loop with Unreachable Exit Condition). This weak­ness indicates improper control flow in DNS packet parsing or response handling that fails to properly validate loop termination conditions. DNS implementations typically parse zone file records, handle recursive queries, or process DNSSEC validation—any of these paths could contain unbounded loops triggered by malformed DNS queries or responses. Without specific CPE data provided, the affected products cannot be definitively identified, but this class of vulnerability commonly affects BIND, Unbound, PowerDNS, systemd-resolved, and other widely-deployed resolver implementations. The infinite loop likely occurs during DNS name compression decompression, DNAME/CNAME chain following, or recursive resolution without proper depth limits.

Affected Products

Specific affected products, versions, and vendor names are not provided in the supplied data. The CVE description references 'the dns implementation' generically, suggesting either: (1) a newly disclosed vulnerability with vendor coordination ongoing; (2) a vulnerability in a foundational library used by multiple DNS implementations (e.g., LDNS, dns-protocol libraries); or (3) a specific product not yet publicly named. Common DNS implementations potentially affected by loop-based DoS vulnerabilities include ISC BIND, NLnet Labs Unbound, PowerDNS, systemd-resolved, and other recursive resolver implementations. Without CPE strings or vendor advisory references, exact affected product versions cannot be determined. Security teams should cross-reference this CVE against advisories from DNS software vendors and their internal inventory of DNS infrastructure.

Remediation

Without vendor advisory links or patch version information provided in the data, specific remediation cannot be prescribed. General remediation steps include: (1) Identify all DNS resolver instances in your infrastructure (both authoritative nameservers and recursive resolvers); (2) Monitor official security advisories from your DNS implementation vendor (ISC, NLnet Labs, PowerDNS, etc.) for patch releases addressing CVE-2025-2962; (3) Apply vendor-supplied patches immediately upon availability, prioritizing production DNS infrastructure; (4) Implement query rate limiting and DNS firewall rules to mitigate infinite-loop triggering queries while patches are pending; (5) Monitor DNS service logs for signs of resource exhaustion or unusual query patterns. Contact your DNS software vendor directly for patch availability and timeline if not yet publicly available.

Priority Score

58
Low Medium High Critical
KEV: 0
EPSS: +0.0
CVSS: +38
POC: +20

Share

CVE-2025-2962 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy