dbcve.org
CryptolibApplication · Nasa

CVE-2025-46674

CRITICAL · 9.9 CVSS v3.1 Published 2025-04-27
Fix available
A fix is available. Upgrade to 1.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

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 · unedited
NASA CryptoLib before 1.3.2 uses Extended Procedures that are a Work in Progress (not intended for use during flight), potentially leading to a keystream oracle.

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 confidence

NASA CryptoLib before version 1.3.2 contains Extended Procedures that are marked as Work in Progress and not intended for flight operations. These incomplete cryptographic procedures can potentially expose a keystream oracle, allowing attackers to predict or recover keystream data used in encryption and compromise confidentiality of protected communications or data.

MitigationUpgrade to NASA CryptoLib 1.3.2 or later. Disable or remove any usage of Extended Procedures in current implementations, as they are not production-ready and may expose cryptographic weaknesses.

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
CryptolibApplication
Affected:< 1.3.2

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed NASA CryptoLib version
    Review project dependencies, build files, or library manifests to find the version of NASA CryptoLib in use. Check package.json, requirements.txt, CMakeLists.txt, or any dependency lock files for the crypto library version.
    Affected if The installed version is lower than 1.3.2 (e.g., 1.3.1, 1.3.0, or earlier)
  2. Locate Extended Procedures module references
    Search source code for imports or includes of Extended Procedures functionality. Look for terms like 'Extended', 'ExtendedProc', 'experimental', or 'WIP' in cryptographic implementation files.
    Affected if Extended Procedures code or modules are present in the codebase
  3. Check for enabled Extended Procedures configuration
    Inspect configuration files, initialization code, or feature flags that enable Extended Procedures. Look for boolean flags, preprocessor defines, or API calls that activate these procedures.
    Affected if Extended Procedures are explicitly enabled or configured in the application
  4. Identify usage of vulnerable API calls
    Review cryptographic operation code for calls to Extended Procedure functions used for encryption/decryption operations that may expose keystream data.
    Affected if Code calls Extended Procedure encryption APIs that could act as a keystream oracle

You are affected if NASA CryptoLib version is below 1.3.2 AND Extended Procedures are implemented, enabled, or used in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.3.2 or later
Fixed in 1.3.2
Vendor patch github.com →
Interim mitigation

Upgrade to NASA CryptoLib 1.3.2 or later. Disable or remove any usage of Extended Procedures in current implementations, as they are not production-ready and may expose cryptographic weaknesses.

Recommended fix High confidence

1.3.2

  1. Verify current Cryptolib version in use by checking project dependencies or library files
  2. Upgrade Cryptolib to version 1.3.2 or later via project's dependency management system (e.g., package manager, build system)
  3. After upgrade, verify the Extended Procedures (Work in Progress features) are not being used in production code
  4. Rebuild and redeploy any applications using Cryptolib
Caveat Review release notes for 1.3.2 to check for any API or behavioral changes that may affect existing integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cryptolib Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46674 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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