ION-DTN < 4.2.1-a.1 Denial of Service via canonicalizePayloadBlock() Assertion
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| nasa-jpl | ION-DTN | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Nasajpl | Iondtn |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.608% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nasajpl
Nasajpl iondtn |
|
| Vendors & Products |
Nasajpl
Nasajpl iondtn |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ION-DTN before 4.2.1-a.1 contains a denial of service vulnerability that allows unauthenticated remote attackers to crash the ION process by sending a BPv7 bundle with a zero-length payload. The canonicalizePayloadBlock() function in bpsec_util.c passes bundle->payload.length to zco_clone() without validating it against zero, causing a failed CHKZERO assertion that triggers sm_Abort() and terminates the process with SIGABRT before any HMAC verification occurs, requiring no valid key or credential to exploit. | |
| Title | ION-DTN < 4.2.1-a.1 Denial of Service via canonicalizePayloadBlock() Assertion | |
| Weaknesses | CWE-617 | |
| References |
| |
| Metrics |
cvssV3_1
|