{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46673 exists.","fix":"No fix has been published for CVE-2025-46673 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46673 is a medium-severity vulnerability in NASA CryptoLib, published on 27 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46673 and fix it if it is affected.\n\nWhat it is: CVE-2025-46673 is a medium-severity vulnerability in NASA CryptoLib, published on 27 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46673 exists.\n\nAffected product: NASA CryptoLib. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-46673/ (Markdown: https://insights.sbomify.com/CVE-2025-46673/index.md)","id":"CVE-2025-46673","markdown":"https://insights.sbomify.com/CVE-2025-46673/index.md","name":"CVE-2025-46673","record":{"aliases":["GHSA-jvpp-7888-2hgr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NASA CryptoLib","requires_auth":"low_privilege","summary":"Attackers can bypass Space Data Link Security protocol protections by exploiting missing operational state checks in NASA CryptoLib.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cryptolib","vendor":"nasa"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-913","name":"Improper Control of Dynamically-Managed Code Resources"}],"description":"NASA 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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Security feature bypass in CryptoLib","id":"CVE-2025-46673","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"Other in CryptoLib","id":"CVE-2025-46674"},"packages":[],"prev":{"headline":"Business logic in CryptoLib","id":"CVE-2025-46672"},"products":["CryptoLib"],"published":"2025-04-27","related":[{"cvss_score":9.4,"headline":"CryptoLib Has Heap Overflow in Crypto_TM_ProcessSecurity due to Unchecked Secondary Header Length","id":"CVE-2025-30216","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":9.3,"headline":"Heap Buffer Overflow via Incomplete Length Check in `Crypto_TC_ApplySecurity`","id":"CVE-2025-30356","kev_date_added":null,"published":"2025-04-01"},{"cvss_score":8.9,"headline":"CryptoLib's Crypto_TC_ApplySecurity() Has a Heap Buffer Overflow Vulnerability","id":"CVE-2025-29909","kev_date_added":null,"published":"2025-03-17"},{"cvss_score":8.9,"headline":"CryptoLib Has Heap Buffer Overflow in Crypto_AOS_ProcessSecurity Function","id":"CVE-2025-29911","kev_date_added":null,"published":"2025-03-17"},{"cvss_score":8.9,"headline":"CryptoLib Has Heap Buffer Overflow Due to Unsigned Integer Underflow in Crypto_TC_ProcessSecurity","id":"CVE-2025-29912","kev_date_added":null,"published":"2025-03-17"},{"cvss_score":8.9,"headline":"CryptoLib's Crypto_TC_Prep_AAD Has Buffer Overflow Due to Integer Underflow","id":"CVE-2025-29913","kev_date_added":null,"published":"2025-03-17"},{"cvss_score":8.8,"headline":"CryptoLib vulnerable to Stack Buffer Overflow in Crypto_Key_Update due to missing TLV length check","id":"CVE-2025-64096","kev_date_added":null,"published":"2025-10-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-29","vendors":["NASA"]},"summary":"Attackers can bypass Space Data Link Security protocol protections by exploiting missing operational state checks in NASA CryptoLib.","url":"https://insights.sbomify.com/CVE-2025-46673/"}