CVE-2025-46673
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 · uneditedNASA CryptoLib before 1.3.2 does not check whether the SA is in an operational state before use, possibly leading to a bypass of the Space Data Link Security protocol (SDLS).
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 · moderate confidenceNASA CryptoLib before version 1.3.2 fails to validate the operational state of Security Associations (SAs) before using them in the Space Data Link Security (SDLS) protocol. This missing state check could allow operations to proceed with non-operational SAs, potentially bypassing the security protections intended by SDLS.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.3.2CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 NASA CryptoLib versionLocate the NASA CryptoLib library or package in your environment and retrieve its version number. Common methods include checking the library file metadata, using a package manager command (e.g., pip show, npm list, or equivalent), or reviewing version information in build configuration files.Affected if The installed version is prior to 1.3.2 (e.g., 1.3.1, 1.3.0, or earlier)
-
Confirm SDLS protocol usageInspect your configuration files, initialization scripts, or runtime settings to determine whether the Space Data Link Security (SDLS) protocol is enabled or being used in your implementation.Affected if SDLS protocol is actively configured or in use with the vulnerable CryptoLib version
-
Review SA state validation logicExamine your codebase or configuration where Security Associations (SAs) are created, managed, or invoked. Look for explicit checks that verify an SA is in an operational or active state before it is used for SDLS operations.Affected if No code or configuration explicitly validates SA operational state prior to use, or such validation is missing entirely
-
Check for manual SA state validation workaroundsSearch your implementation for any custom validation functions, scripts, or middleware that manually verify SA state before invoking CryptoLib functions for SDLS.Affected if No manual validation mechanism exists and the CryptoLib version is below 1.3.2
You are affected if NASA CryptoLib version is below 1.3.2 AND the SDLS protocol is being used without any external SA state validation in place.
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 · scoped1.3.2
Upgrade to NASA CryptoLib version 1.3.2 or later which implements proper SA state validation before use.
NASA CryptoLib 1.3.2
- Identify all projects and dependencies that include NASA CryptoLib version before 1.3.2
- Update the Cryptolib dependency to version 1.3.2 or later in your project configuration (e.g., package.json, requirements.txt, or submodule)
- Rebuild and recompile any software that links against Cryptolib
- Verify the SA state checking is now properly enforced before use in your implementation
- Test SDLS protocol functionality to confirm the security bypass is resolved
- Audit other security associations (SAs) to ensure they are properly configured and in operational state before use
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46673 — 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-2025-46673 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