{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25942 exists.","fix":"No fix has been published for CVE-2025-25942 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25942 is a medium-severity vulnerability in Axiosys Bento4, published on 19 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-25942 and fix it if it is affected.\n\nWhat it is: CVE-2025-25942 is a medium-severity vulnerability in Axiosys Bento4, published on 19 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25942 exists.\n\nAffected product: Axiosys Bento4. 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-25942/ (Markdown: https://insights.sbomify.com/CVE-2025-25942/index.md)","id":"CVE-2025-25942","markdown":"https://insights.sbomify.com/CVE-2025-25942/index.md","name":"CVE-2025-25942","record":{"aliases":["GHSA-wr4v-2x2x-cprg"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Bento4 media library","requires_auth":"none","summary":"An attacker can obtain sensitive information by processing invalid files with the mp4fragment tool due to improper memory release.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bento4","vendor":"axiosys"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue in Bento4 v1.6.0-641 allows an attacker to obtain sensitive information via the the mp4fragment tool when processing invalid files. Specifically, memory allocated in SampleArray::SampleArray in Mp4Fragment.cpp is not properly released.","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":"Information disclosure in n/a","id":"CVE-2025-25942","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"axiosys:bento4","products":["axiosys:bento4"],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-25943"},"packages":[],"prev":{"headline":"Deserialization in n/a","id":"CVE-2025-25940"},"products":["n/a"],"published":"2025-02-19","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-31002","kev_date_added":null,"published":"2024-04-02"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14531","kev_date_added":null,"published":"2018-07-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14532","kev_date_added":null,"published":"2018-07-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-13846","kev_date_added":null,"published":"2018-07-10"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2024-31003","kev_date_added":null,"published":"2024-04-02"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2024-31004","kev_date_added":null,"published":"2024-04-02"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2022-41428","kev_date_added":null,"published":"2022-10-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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-20","vendors":["n/a"]},"summary":"An attacker can obtain sensitive information by processing invalid files with the mp4fragment tool due to improper memory release.","url":"https://insights.sbomify.com/CVE-2025-25942/"}