Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach µD3TN TCPCLv3 listener
-
DeliveryInitiate TCPCL handshake
-
ExploitSend crafted oversized length field
-
ExecutionTrigger integer overflow in allocation
-
PersistHeap overflow crashes daemon
-
ImpactDenial of service on DTN node
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires network reachability to a µD3TN v0.15.0 node running the TCP Convergence Layer version 3 (TCPCLv3) with its listener exposed; the attacker sends a crafted handshake whose length/size values trigger the CWE-190 integer overflow. No authentication and no user interaction are required (PR:N/UI:N), so any host that can reach the TCPCL port can attempt it. Limiting factors: exploitation only affects deployments that actually run TCPCLv3 (rather than other convergence layers or transports) and that expose the listener to the attacker's network, and impact is confined to availability (daemon crash) with no confidentiality or integrity effect and no code execution indicated. |
| Impact | The single strongest signal is the CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5), which describes a remote, unauthenticated, low-complexity condition with no user interaction and a pure availability impact (C:N/I:N/A:H) - consistent with the description of an integer overflow leading to a heap overflow that 'reliably' causes DoS during the TCPCLv3 handshake. No EPSS score, no CISA KEV listing, and no public exploit (POC) are provided in the intelligence, so this is 'no public exploit identified at time of analysis' and there is no evidence of active exploitation. No SSVC decision data is supplied. The realistic priority is therefore moderate-to-high on paper but tempered heavily by deployment footprint: µD3TN is a niche Delay/Disruption-Tolerant Networking (Bundle Protocol) implementation used mainly in space, research, and experimental networks, not general enterprise infrastructure, so the real-world blast radius is small despite the network-reachable unauthenticated vector. The vendor's word 'reliably' suggests a dependable crash primitive, which raises confidence in the DoS but there is no indication of code execution - impact is availability only, so this is a service-crash issue rather than an RCE. Key missing data: EPSS, KEV, POC, and an independently confirmed patched version are all absent; the sole reference is a GitLab work-item (issue tracker), not a formal advisory. |
| Exploit ScenarioDerived | An attacker with network reachability to a µD3TN node's TCP Convergence Layer (TCPCLv3) listener initiates a handshake and sends crafted length/size fields that trigger the integer overflow, producing an undersized heap allocation and subsequent heap overflow that crashes the daemon. Because the vector is remote and unauthenticated (PR:N/UI:N) and the vendor states the DoS is triggered 'reliably', a single malformed handshake can repeatedly take the node offline. No public proof-of-concept is referenced at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Remote unauthenticated denial of service in µD3TN v0.15.0: an integer overflow (CWE-190) in the TCPCLv3 handshake processing path leads to a heap overflow that, per the reported analysis, reliably crashes the daemon. Any host able to reach a µD3TN node's TCPCLv3 listener can trigger it without credentials or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), but the impact is confined to availability - no confidentiality or integrity loss and no code execution is indicated. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV); exploitation also requires the deployment to actually run TCPCLv3 rather than another convergence layer.
RemediationAI
No vendor-released patch was identified at time of analysis - the only supplied reference is the upstream GitLab work item https://gitlab.com/d3tn/ud3tn/-/work_items/287, which should be monitored for a fixed release and for confirmation of the exact affected version range. Until a patch ships, the highest-value compensating control is to remove network exposure of the TCPCLv3 listener: bind it to loopback or to a management interface and filter the TCPCL port at the host firewall so that only known peer nodes can open handshakes, which directly blocks the unauthenticated remote attack precondition at the cost of breaking legitimate DTN peering from untrusted or mobile nodes. Where TCPCLv3 is not strictly required, disable the convergence layer entirely or switch to an alternate transport that is not affected by this code path - the trade-off is loss of interoperability with peers that only speak TCPCLv3. If the listener must remain reachable, place it behind a TCP proxy or VPN/overlay with peer allow-listing and connection rate limiting, accepting that a determined on-path attacker within the allowed set can still crash the daemon, and add process supervision (systemd Restart=on-failure or an equivalent watchdog) plus alerting so that a successful denial-of-service attempt results in rapid automatic recovery rather than prolonged outage. Note that restart-based recovery does not prevent the crash itself, does not address the underlying integer overflow, and should be treated purely as availability insurance; no authentication, configuration flag, or input-validation workaround was identified in the supplied data that would let an operator safely keep an unpatched TCPCLv3 listener exposed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
µD3TN is a Delay-Tolerant Networking (DTN) implementation maintained by D3TN GmbH, designed for store-and-forward communications over challenged or intermittent links such as space, IoT and tactical networks. DTN stacks like µD3TN are modular: a Bundle Protocol agent is paired with one or more Convergence Layers that adapt the bundle protocol to a specific transport, and TCPCLv3 is the TCP-based Convergence Layer (the version 3 handshake defined by the DTN TCPCL specification, RFC 9174). During that handshake the peers exchange session parameters including length and message-size fields; µD3TN v0.15.0 performs arithmetic on those attacker-supplied size values without adequate bounds checking, so an oversized or crafted value wraps around (CWE-190, integer overflow), and the resulting under-sized buffer computation is used for a heap allocation that the subsequent copy overruns. The weakness class is therefore an integer overflow that manifests as a heap-based buffer overflow in the handshake parser, which is why the impact is a deterministic daemon crash rather than memory-corruption-mediated code execution. The CPE cpe:2.3:a:d3tn_gmbh:µd3tn:*:*:*:*:*:*:*:* is broad, but the reporter attributes the flaw specifically to v0.15.0; the affected component is the TCPCLv3 convergence layer listener, not the core bundle processing or other convergence layers.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Remote unauthenticated handshake with no user interaction (AV:N/AC:L/PR:N/UI:N); reliable crash gives A:H with no confidentiality or integrity impact and no scope change.
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
Lifecycle Timeline
2DescriptionCVE.org
Integer overflow in µD3TN v0.15.0 TCPCLv3 handshake causes heap overflow, allowing remote attackers to reliably cause DoS
Executive ViewAI
A high-severity flaw in the µD3TN disruption-tolerant networking daemon (v0.15.0) allows any host that can reach a node's TCPCLv3 listener to crash it without authentication or user interaction, making it a pure availability risk for connected environments. Only deployments that actually enable the TCPCLv3 convergence layer are exposed, and no evidence of data theft, tampering, or code execution has been reported, so leadership should treat this as a service-continuity and network-resilience issue rather than a data-breach event.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network reachability to the µD3TN TCPCLv3 listener with firewall/ACL rules limited to trusted peers; disable the TCPCLv3 convergence layer or switch to an alternate convergence layer where operationally feasible; rate-limit or throttle inbound connections to the listener; enable automatic service restart and health monitoring to shorten outage duration; and monitor for malformed handshake traffic and repeated daemon crashes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
EUVD-2026-82978
GHSA-mf4m-237x-h46p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB