{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2004-1309 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2004-1309 is a critical memory corruption vulnerability in n/a, published on 22 Dec 2004. 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-2004-1309 and fix it if it is affected.\n\nWhat it is: CVE-2004-1309 is a critical memory corruption vulnerability in n/a, published on 22 Dec 2004. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2004-1309 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-2004-1309/ (Markdown: https://insights.sbomify.com/CVE-2004-1309/index.md)","id":"CVE-2004-1309","markdown":"https://insights.sbomify.com/CVE-2004-1309/index.md","name":"CVE-2004-1309","record":{"aliases":["DEBIAN-CVE-2004-1309","GHSA-xxfg-v7qr-vxwh"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MPlayer media player","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious BMP file in MPlayer.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"unix_mplayer","vendor":"mplayer"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Heap-based buffer overflow in the demux_open_bmp function in demux_bmp.c for Unix MPlayer 1.0pre5 allows remote attackers to execute arbitrary code via a bitmap (BMP) file containing a large biClrUsed field.","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":"Memory corruption in n/a","id":"CVE-2004-1309","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2004"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2004-1310"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2004-1308"},"products":["n/a"],"published":"2004-12-22","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious BMP file in MPlayer.","url":"https://insights.sbomify.com/CVE-2004-1309/"}