ION-DTN 2.2.1b-4.2.0 Integer Overflow Heap Corruption via DGR
Affects ION-DTN 2.2.1b through 4.2.0 where DGR runs over internal IPC or custom transports. Fixed in 4.2.1-a.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.2.1-a.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.2.1-a.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
ION-DTN, NASA JPL's delay-tolerant networking software, has a heap corruption flaw in its Datagram Retransmission convergence layer that an attacker can trigger remotely, without logging in, by sending a crafted datagram. Successful exploitation can cause denial of service or potentially remote code execution.
Read the original description
NASA JPL ION-DTN 2.2.1b through 4.2.0 contains an integer overflow vulnerability in the Datagram Retransmission (DGR) convergence layer that allows attackers to corrupt heap memory by sending a maliciously crafted 64-bit svcDataLength value that wraps a 32-bit allocation size calculation. Attackers can exploit the dgr_receive API's unchecked memcpy operation using synthetic datagrams or DGR traffic over internal IPC or custom transports to trigger an out-of-bounds write, leading to denial of service or potential remote code execution.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.2.1-a.2.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- nasa-jpl ION-DTN
From 2.2.1b · through 4.2.0
Evidence 3
- Advisory
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124001
Is CVE-2026-124001 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An integer overflow in ION-DTN's DGR handling corrupts heap memory. An attacker could cause a denial of service or potentially achieve remote code execution.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124001?
ION-DTN: from 2.2.1b through 4.2.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions 2.2.1b through 4.2.0 are in the affected range. The exposure is tied to DGR over internal IPC or custom transports, while standard UDP deployments were largely protected. Compare your installed ION version against this range and check whether DGR is in use.Source: vulncheck.com, github.com
How do I fix CVE-2026-124001?
Upgrade to ION 4.2.1-a.2. No workaround is listed in the facts provided.Source: vulncheck.com, github.com