{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25372 exists.","fix":"No fix has been published for CVE-2025-25372 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25372 is a high-severity memory corruption vulnerability in n/a, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-25372 and fix it if it is affected.\n\nWhat it is: CVE-2025-25372 is a high-severity memory corruption vulnerability in n/a, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25372 exists.\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-2025-25372/ (Markdown: https://insights.sbomify.com/CVE-2025-25372/index.md)","id":"CVE-2025-25372","markdown":"https://insights.sbomify.com/CVE-2025-25372/index.md","name":"CVE-2025-25372","record":{"aliases":["GHSA-674w-jwj3-6mv7"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"NASA cFS Aquila","requires_auth":"none","summary":"An attacker can cause a segmentation fault in the Memory Management Module by sending a malicious telecommand, leading to denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"core_flight_system","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-787","name":"Out-of-bounds Write"}],"description":"NASA cFS (Core Flight System) Aquila is vulnerable to segmentation fault via sending a malicious telecommand to the Memory Management Module.","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":"Memory corruption in n/a","id":"CVE-2025-25372","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-25373"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2025-25371"},"products":["n/a"],"published":"2025-03-25","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2025-25373","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2025-25371","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-25374","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":5.3,"headline":"NASA cFS CCSDS Packet Header to_lab_passthru_encode.c CFE_MSG_GetSize heap-based overflow","id":"CVE-2026-5474","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":5.1,"headline":"NASA cFS CCSDS Header Size cfe_sb_priv.c CFE_SB_TransmitMsg memory corruption","id":"CVE-2026-5475","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":2.1,"headline":"NASA cFS cfe_tbl_passthru_codec.c CFE_TBL_ValidateCodecLoadSize integer overflow","id":"CVE-2026-5476","kev_date_added":null,"published":"2026-04-03"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-26","vendors":["n/a"]},"summary":"An attacker can cause a segmentation fault in the Memory Management Module by sending a malicious telecommand, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2025-25372/"}