VulnerabilityPublished 25 Jul 2025

CVE-2025-8183: µD3TN · NULL Pointer Dereference

Affects µD3TNSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubd3tn/ud3tn`pkg:github/d3tn/ud3tn`Other threats	Affected =0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of an official patch at the time of disclosure, European organizations should implement several practical mitigations: 1) Network-level filtering: Restrict and monitor incoming traffic to µD3TN endpoints, especially from untrusted or external networks, to reduce exposure to remote attacks. 2) Input validation and sanitization: If possible, configure µD3TN or its environment to validate endpoint identifiers and reject malformed or unexpected inputs before processing. 3) Service isolation and redundancy: Deploy µD3TN services in isolated environments or containers to limit the blast radius of a crash, and implement redundancy or failover mechanisms to maintain availability during an attack. 4) Monitoring and alerting: Establish monitoring for µD3TN service crashes or abnormal behavior to detect potential exploitation attempts promptly. 5) Vendor engagement: Maintain communication with D3TN GmbH for updates on patches or mitigations, and apply official fixes as soon as they become available. 6) Incident response preparation: Develop and test response plans for DoS scenarios affecting µD3TN to minimize operational impact. These steps go beyond generic advice by focusing on network segmentation, proactive input handling, and operational resilience tailored to the nature of this vulnerability.

Description

NULL Pointer Dereference in µD3TN via non-singleton destination Endpoint Identifier allows remote attacker to reliably cause DoS

Impact

For European organizations, the impact of CVE-2025-8183 can be significant if they rely on µD3TN for critical communication infrastructure or network services. µD3TN is a software implementation related to Delay-Tolerant Networking (DTN), which is often used in environments with intermittent connectivity or challenging network conditions, such as research institutions, space agencies, or specialized industrial applications. A successful exploitation would cause denial of service, potentially disrupting communication channels, data transfers, or operational processes dependent on µD3TN. This could lead to operational downtime, loss of productivity, and in sensitive environments, could impair mission-critical functions. Since the vulnerability does not affect confidentiality or integrity, the primary concern is service availability. European organizations involved in advanced networking research, aerospace, or critical infrastructure sectors using µD3TN could face increased risk of service outages. Additionally, the ease of exploitation without authentication or user interaction raises the risk of automated attacks or scanning by malicious actors. Although no known exploits are reported yet, the public disclosure and high CVSS score suggest that threat actors may develop exploits in the future, increasing the urgency for mitigation.

CWE-476NULL Pointer Dereference (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #13OWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product dereferences a pointer that it expects to be valid but is NULL.
Implementation
For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
Requirements
Select a programming language that is not susceptible to these issues.
Implementation
Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gitlab.com/d3tn/ud3tn/-/issues/255 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Jul 2025, 10:02 UTC

WeaknessesCWE-476

Technical details

References

Community reviews

Related threats