{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-125019 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-125019 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-125019 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 19 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-125019 and fix it if it is affected.\n\nWhat it is: CVE-2014-125019 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 19 Jun 2022. 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-2014-125019 in the wild and no public exploit code.\n\nAffected product: Ffmpeg Ffmpeg. 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-2014-125019/ (Markdown: https://insights.sbomify.com/CVE-2014-125019/index.md)","id":"CVE-2014-125019","markdown":"https://insights.sbomify.com/CVE-2014-125019/index.md","name":"CVE-2014-125019","record":{"aliases":["GHSA-8jff-rjf4-c2vg"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"FFmpeg media library","requires_auth":"none","summary":"Remote attackers can trigger memory corruption in FFmpeg's slice segment handler, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"ffmpeg","vendor":"ffmpeg"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A vulnerability, which was classified as problematic, was found in FFmpeg 2.0. This affects the function decode_nal_unit of the component Slice Segment Handler. The manipulation leads to memory corruption. It is possible to initiate the attack remotely. It is recommended to apply a patch to fix this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"FFmpeg Slice Segment decode_nal_unit memory corruption","id":"CVE-2014-125019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ffmpeg:ffmpeg","products":["ffmpeg:ffmpeg"],"type":"memory_corruption","year":"2014"},"n_packages":0,"n_references":2,"next":{"headline":"FFmpeg decode_update_thread_context memory corruption","id":"CVE-2014-125020"},"packages":[],"prev":{"headline":"FFmpeg decode_slice_header memory corruption","id":"CVE-2014-125018"},"products":["FFmpeg"],"published":"2022-06-19","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-0864","kev_date_added":null,"published":"2013-11-23"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-0872","kev_date_added":null,"published":"2013-11-23"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-0873","kev_date_added":null,"published":"2013-11-23"},{"cvss_score":10,"headline":"Null dereference in n/a","id":"CVE-2013-4265","kev_date_added":null,"published":"2013-11-23"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2011-3937","kev_date_added":null,"published":"2013-01-05"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-2772","kev_date_added":null,"published":"2012-09-10"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-2775","kev_date_added":null,"published":"2012-09-10"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["unspecified"]},"summary":"Remote attackers can trigger memory corruption in FFmpeg's slice segment handler, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2014-125019/"}