{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57612 exists.","fix":"No fix has been published for CVE-2025-57612 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-57612 is a high-severity vulnerability in n/a, published on 2 Sep 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-57612 and fix it if it is affected.\n\nWhat it is: CVE-2025-57612 is a high-severity vulnerability in n/a, published on 2 Sep 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-57612 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-57612/ (Markdown: https://insights.sbomify.com/CVE-2025-57612/index.md)","id":"CVE-2025-57612","markdown":"https://insights.sbomify.com/CVE-2025-57612/index.md","name":"CVE-2025-57612","record":{"aliases":["GHSA-r5mw-v3mq-jrvm"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust FFmpeg bindings","requires_auth":"none","summary":"A null pointer dereference in the name() method allows attackers to cause a denial of service by providing an unrecognized sample format.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rust-ffmpeg","vendor":"meh.schizofreni"}],"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-476","name":"NULL Pointer Dereference"}],"description":"An issue was discovered in rust-ffmpeg 0.3.0 (after comit 5ac0527) Null pointer dereference vulnerability in the name() method allows an attacker to cause a denial of service. The vulnerability exists because the method fails to check for a NULL return value from the av_get_sample_fmt_name() C function, which can be triggered by providing an unrecognized sample format.","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":"Null dereference in n/a","id":"CVE-2025-57612","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2025-57613"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2025-57611"},"products":["n/a"],"published":"2025-09-02","related":[{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-57613","kev_date_added":null,"published":"2025-09-02"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2025-57614","kev_date_added":null,"published":"2025-09-02"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2025-57615","kev_date_added":null,"published":"2025-09-02"},{"cvss_score":7.5,"headline":"Use after free in n/a","id":"CVE-2025-57616","kev_date_added":null,"published":"2025-09-02"},{"cvss_score":5.3,"headline":"Null dereference in n/a","id":"CVE-2025-57611","kev_date_added":null,"published":"2025-09-02"}],"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-09-02","vendors":["n/a"]},"summary":"A null pointer dereference in the name() method allows attackers to cause a denial of service by providing an unrecognized sample format.","url":"https://insights.sbomify.com/CVE-2025-57612/"}