CryptoLib Has Heap Overflow in Crypto_TM_ProcessSecurity due to Unchecked Secondary Header Length
CryptoLib provides a software-only solution using the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between a spacecraft running the core Flight System (cFS) and a ground station. In versions 1.3.3 and prior, a Heap Overflow vulnerability occurs in the `Crypto_TM_ProcessSecurity` function (`crypto_tm.c:1735:8`). When processing the Secondary Header Length of a TM protocol packet, if the Secondary Header Length exceeds the packet's total length, a heap overflow is triggered during the memcpy operation that copies packet data into the dynamically allocated buffer `p_new_dec_frame`. This allows an attacker to overwrite adjacent heap memory, potentially leading to arbitrary code execution or system instability. A patch is available at commit 810fd66d592c883125272fef123c3240db2f170f.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-30216
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 14:53 UTC · Revision 1
Source evidence
CryptoLib Has Heap Overflow in Crypto_TM_ProcessSecurity due to Unchecked Secondary Header Length
core-osv · Original sourcePublished 25 Mar 2025, 19:22 UTC
CryptoLib provides a software-only solution using the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between a spacecraft running the core Flight System (cFS) and a ground station. In versions 1.3.3 and prior, a Heap Overflow vulnerability occurs in the `Crypto_TM_ProcessSecurity` function (`crypto_tm.c:1735:8`). When processing the Secondary Header Length of a TM protocol packet, if the Secondary Header Length exceeds the packet's total length, a heap overflow is triggered during the memcpy operation that copies packet data into the dynamically allocated buffer `p_new_dec_frame`. This allows an attacker to overwrite adjacent heap memory, potentially leading to arbitrary code execution or system instability. A patch is available at commit 810fd66d592c883125272fef123c3240db2f170f.
osv:CVE-2025-30216
Complete source record
{
"id": "c3ac86442a3751aa5defddf34d1843d6b69f2ef9cdbcce3e65c79a5a6a384f1e",
"url": "https://osv.dev/vulnerability/CVE-2025-30216",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CryptoLib Has Heap Overflow in Crypto_TM_ProcessSecurity due to Unchecked Secondary Header Length",
"summary": "CryptoLib provides a software-only solution using the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between a spacecraft running the core Flight System (cFS) and a ground station. In versions 1.3.3 and prior, a Heap Overflow vulnerability occurs in the `Crypto_TM_ProcessSecurity` function (`crypto_tm.c:1735:8`). When processing the Secondary Header Length of a TM protocol packet, if the Secondary Header Length exceeds the packet's total length, a heap overflow is triggered during the memcpy operation that copies packet data into the dynamically allocated buffer `p_new_dec_frame`. This allows an attacker to overwrite adjacent heap memory, potentially leading to arbitrary code execution or system instability. A patch is available at commit 810fd66d592c883125272fef123c3240db2f170f.",
"evidence": "osv:CVE-2025-30216",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2025-30216",
"aliases": [
"CVE-2025-30216",
"GHSA-v3jc-5j74-hcjv"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/nasa/cryptolib",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "0d58c9a8cb9f7e96d67858d7ac125daaec0ca299"
},
{
"fixed": "810fd66d592c883125272fef123c3240db2f170f"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:nasa:cryptolib:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.4.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "810fd66d592c883125272fef123c3240db2f170f"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v1.3.3",
"v1.3.2",
"v1.3.1",
"v1.3.0",
"v1.2.3",
"v1.2.2",
"v1.2.1",
"v1.2.0",
"v1.1.1",
"v1.1.0",
"v1.0.3"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-30216.json"
}
}
],
"modified": "2026-10-28T02:30:29.740089576Z",
"provider": "osv",
"references": [
"https://github.com/user-attachments/assets/d49cea04-ce84-4d60-bb3a-987e843f09c4",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/30xxx/CVE-2025-30216.json",
"https://github.com/nasa/CryptoLib/security/advisories/GHSA-v3jc-5j74-hcjv",
"https://nvd.nist.gov/vuln/detail/CVE-2025-30216",
"https://github.com/nasa/CryptoLib/commit/810fd66d592c883125272fef123c3240db2f170f"
],
"provider_metadata": {
"cwe_ids": [
"CWE-122"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/30xxx/CVE-2025-30216.json"
}
},
"related_cves": [
{
"value": "CVE-2025-30216",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 496558,
"published_at": "2025-03-25T19:22:22.645+00:00"
}