{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-25473 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-25473 is a medium-severity vulnerability in n/a, published on 18 Feb 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-25473 and fix it if it is affected.\n\nWhat it is: CVE-2025-25473 is a medium-severity vulnerability in n/a, published on 18 Feb 2025. 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-2025-25473 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-2025-25473/ (Markdown: https://insights.sbomify.com/CVE-2025-25473/index.md)","id":"CVE-2025-25473","markdown":"https://insights.sbomify.com/CVE-2025-25473/index.md","name":"CVE-2025-25473","record":{"aliases":["DEBIAN-CVE-2025-25473","GHSA-c92g-p5cr-cr59","UBUNTU-CVE-2025-25473"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"FFmpeg multimedia library","requires_auth":"none","summary":"A null pointer dereference in FFmpeg's memory management can cause a denial of service when processing media files.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"FFmpeg git master before commit c08d30 was discovered to contain a memory leak in the avformat_free_context function in libavutil/mem.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":true,"headline":"Null dereference in n/a","id":"CVE-2025-25473","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-25474"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-25472"},"products":["n/a"],"published":"2025-02-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-12-16","vendors":["n/a"]},"summary":"A null pointer dereference in FFmpeg's memory management can cause a denial of service when processing media files.","url":"https://insights.sbomify.com/CVE-2025-25473/"}