{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-44911 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-44911 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-44911 is a high-severity memory corruption vulnerability in n/a, published on 27 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-44911 and fix it if it is affected.\n\nWhat it is: CVE-2024-44911 is a high-severity memory corruption vulnerability in n/a, published on 27 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-44911 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2024-44911/ (Markdown: https://insights.sbomify.com/CVE-2024-44911/index.md)","id":"CVE-2024-44911","markdown":"https://insights.sbomify.com/CVE-2024-44911/index.md","name":"CVE-2024-44911","record":{"aliases":["GHSA-8x7j-q7w2-6pxg"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"NASA CryptoLib","requires_auth":"none","summary":"An out-of-bounds read in NASA CryptoLib's TC subsystem can lead to crashes or information disclosure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cryptolib","vendor":"nasa"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"NASA CryptoLib v1.3.0 was discovered to contain an Out-of-Bounds read via the TC subsystem (crypto_tc.c).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in n/a","id":"CVE-2024-44911","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2024-44912"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-44910"},"products":["n/a"],"published":"2024-09-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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-18","vendors":["n/a"]},"summary":"An out-of-bounds read in NASA CryptoLib's TC subsystem can lead to crashes or information disclosure.","url":"https://insights.sbomify.com/CVE-2024-44911/"}