CryptoLib provides a software-only solution using the CCSDS Space Data Link Security Protocol - Extended…

CVE-2025-29912 is a heap buffer overflow in NASA's CryptoLib, an open-source implementation of the CCSDS Space Data Link Security Protocol – Extended Procedures (SDLS-EP) used to protect telecommand/telemetry links between spacecraft and ground stations. The bug lives in Crypto_TM_ProcessSecurity (crypto_tm.c:1735): the Secondary Header Length field is masked with & 0x3F (capping at 64) but the code never verifies that 6 + secondary_hdr_len stays inside the ingested packet buffer, so a crafted TM frame causes memcpy to write past the allocated heap chunk. Affected versions are 1.3.3 and earlier; the fix landed in the post-1.3.3 mainline, though follow-on CVEs (CVE-2025-29909, -30216, -30356) show the surrounding parsing code needed additional hardening.

The vendor CVSS of 9.8 (AV:N/AC:L/PR:N/UI:N) is technically correct — the parser takes attacker-controlled bytes with no auth — but the network vector is a purpose-built spacecraft link, not the public internet or a corporate LAN. For the ~0.001% of the world that operates ground station software linking cFS-based spacecraft, this is genuinely critical. For the enterprise defender with 10,000 Windows/Linux hosts, RHEL boxes, and Kubernetes clusters, CryptoLib will not appear on your SBOM. The score is real; the reachable population is not.

Why this verdict

• Reachable population is effectively zero for enterprise IT. CryptoLib is not in RHEL, Ubuntu, Debian, Alpine, or any major container base image. It ships only with NASA cFS and aerospace forks.
• Network vector is not the Internet. AV:N in CVSS terminology means "across a network" — here that network is a CCSDS TM link, reached via RF, mission fiber, or an insider on the ground segment. There is no shodan-scannable attack surface.
• Role multiplier — flight/ground software: On a NASA cFS spacecraft or a mission control ground station, the chain succeeds and blast radius is spacecraft compromise / telemetry corruption / potential safety-of-flight impact. That is a genuine floor of CRITICAL for aerospace operators, but the canonical component base is aerospace-only — general enterprises hold ~0% share, so the enterprise verdict floor drops out.
• No KEV, EPSS 1.1%, no weaponized PoC. Zero indicators of opportunistic exploitation.
• Follow-on CVEs (29909/30216/30356) mean the fix chain must be tracked as a set — patching only 29912 leaves siblings open. This is a maintenance note, not a severity driver.

Why not higher?

MEDIUM or higher would require either a plausible enterprise SBOM footprint (there is none) or evidence of active exploitation against ground stations (there is none). CRITICAL would require the CryptoLib parser to be reachable from the public internet on typical corporate infrastructure, which it is not.

Why not lower?

Not IGNORE because aerospace defenders, cubesat operators, and defense/space primes DO run this code and for them a crafted TM frame ending in heap corruption of the security frontend is a real safety-relevant bug. Documenting rationale without action would be wrong for that sub-population.

1. Inventory: confirm CryptoLib is not on your SBOM — Run syft / grype / trivy across build artifacts and container images searching for cryptolib, crypto_tm.c, Crypto_TM_ProcessSecurity, and NASA cFS signatures. If nothing hits — and it won't in 99.99% of enterprises — close the ticket with rationale. Complete inventory sweep within the noisgate LOW backlog window (no SLA).
2. If you DO ship CryptoLib: upgrade past 1.3.3 and pull sibling CVE fixes — Track the nasa/CryptoLib main branch and pull the fixes for CVE-2025-29909, -29912, -30216, and -30356 as a set — patching only one leaves the parser exploitable via a neighboring code path. For aerospace operators this is a CRITICAL for you and should be handled under noisgate mitigation SLA ≤ 3 days.
3. Enforce upstream frame-length validation — Wrap Crypto_TM_ProcessSecurity in a caller-side length check that rejects any frame whose declared secondary header length exceeds len_ingest - 6. This is a durable defense across the sibling CVEs and takes effect immediately without waiting on a library release.
4. Rebuild with hardening flags — Compile flight/ground builds with -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wl,-z,relro,-z,now and, on ground-station Linux, enable ASan in test rigs. Reduces the exploitability of any residual parser bug.

Run this on any Linux build server, container-image scanner host, or ground-station box. It searches installed binaries and source trees for CryptoLib and reports the version. Invoke as ./check-cryptolib.sh /opt /usr/local /srv/cfs. No root required for read-only scans; use root if you need to walk /opt on locked-down systems.

#!/usr/bin/env bash
# noisgate: CVE-2025-29912 CryptoLib presence + version check
# Usage: ./check-cryptolib.sh [paths...]
# Exit: 0 PATCHED/absent, 1 VULNERABLE, 2 UNKNOWN
set -u
PATHS=("${@:-/opt /usr/local /usr/lib /srv}")
STATUS=0
FOUND=0

version_lte_133() {
  # returns 0 if $1 <= 1.3.3
  local v=$1
  printf '%s\n1.3.3\n' "$v" | sort -V | head -1 | grep -qx "$v"
}

for P in "${PATHS[@]}"; do
  [ -d "$P" ] || continue
  # binary/library search
  while IFS= read -r hit; do
    FOUND=1
    echo "[hit] $hit"
    # try to extract a version string embedded in the binary
    v=$(strings "$hit" 2>/dev/null | grep -Eo 'CryptoLib[[:space:]]*v?[0-9]+\.[0-9]+\.[0-9]+' | head -1 | grep -Eo '[0-9]+\.[0-9]+\.[0-9]+')
    if [ -n "$v" ]; then
      if version_lte_133 "$v"; then
        echo "VULNERABLE: CryptoLib $v at $hit (<=1.3.3)"
        STATUS=1
      else
        echo "PATCHED: CryptoLib $v at $hit"
      fi
    else
      echo "UNKNOWN version for $hit — inspect manually"
      [ $STATUS -eq 0 ] && STATUS=2
    fi
  done < <(find "$P" -type f \( -name 'libcryptolib*' -o -name 'cryptolib*' -o -name 'crypto_tm.c' \) 2>/dev/null)
done

if [ $FOUND -eq 0 ]; then
  echo "PATCHED: CryptoLib not present in scanned paths — this host is not affected."
  exit 0
fi
exit $STATUS

Sources

1. NVD — CVE-2025-29912
2. GitHub Security Advisory GHSA-v3jc-5j74-hcjv
3. Red Hat Security — CVE-2025-29912
4. nasa/CryptoLib releases
5. Sibling advisory GHSA-3f5x-r59x-p8cf (Crypto_TC_ProcessSecurity)
6. Sibling advisory GHSA-q4v2-fvrv-qrf6 (Crypto_TC_Prep_AAD)
7. AISLE research on NASA CryptoLib (CVE-2025-59534)
8. CCSDS SDLS-EP Blue Book (355.1-B-1)