CVE-2024-54130
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe NASA’s Interplanetary Overlay Network (ION) is an implementation of Delay/Disruption Tolerant Networking (DTN). A segmentation fault occurs with ION-DTN BPv7 software version 4.1.3 when a bundle with a Destination Endpoint ID (EID) set to dtn:none is received. This causes the node to become unresponsive to incoming bundles, leading to a Denial of Service (DoS) condition. This vulnerability is fixed in 4.1.3s.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNASA's ION DTN implementation version 4.1.3 suffers from a segmentation fault when processing bundles with a Destination Endpoint ID set to 'dtn:none', causing the node to crash and become unresponsive to all incoming traffic, resulting in a critical DoS condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ION DTN software versionRun the ionversion command or check the package metadata (dpkg -l, rpm -qi, or examine the binary version string if available)Affected if The installed version is exactly 4.1.3
-
Confirm ION DTN service is runningCheck for ion processes (ps aux | grep ion) or the listening DTN port (typically 4556 for bpv7)Affected if ION DTN daemon is actively running and accepting connections
-
Determine if DTN bundle reception is enabledReview the ionsecrc configuration file and verify bpv7 reception is not disabled (look for 'bpv7 disable' or similar settings)Affected if Bundle reception is enabled - the node will process incoming bundles including those with dtn:none destination
A system is affected if it runs ION DTN version 4.1.3 with the bundle reception service enabled, allowing it to process incoming bundles that could trigger the segmentation fault when the Destination Endpoint ID is set to 'dtn:none'.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade ION-DTN BPv7 software from version 4.1.3 to version 4.1.3s which contains the fix for this vulnerability.
4.1.3s
- 1. Identify the current version of ION-DTN BPv7 software installed on the system
- 2. Download ION-DTN BPv7 version 4.1.3s or later from the official GitHub repository
- 3. Backup current ION configuration files and data
- 4. Stop the ION-DTN service
- 5. Install version 4.1.3s following standard installation procedures
- 6. Restore configuration files if needed
- 7. Start the ION-DTN service
- 8. Verify the service is running and test with a bundle containing Destination EID 'dtn:none' to confirm the vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data