{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6251 exists.","fix":"No fix has been published for CVE-2006-6251 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-6251 is a high-severity memory corruption vulnerability in n/a, published on 4 Dec 2006. 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-2006-6251 and fix it if it is affected.\n\nWhat it is: CVE-2006-6251 is a high-severity memory corruption vulnerability in n/a, published on 4 Dec 2006. 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-2006-6251 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-2006-6251/ (Markdown: https://insights.sbomify.com/CVE-2006-6251/index.md)","id":"CVE-2006-6251","markdown":"https://insights.sbomify.com/CVE-2006-6251/index.md","name":"CVE-2006-6251","record":{"aliases":["GHSA-pv28-rrgx-vv29"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Media player","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious M3U file in VUPlayer.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vuplayer","vendor":"vuplayer"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Stack-based buffer overflow in VUPlayer 2.44 and earlier allows remote attackers to execute arbitrary code via a long string in an M3U file, aka an \"M3U UNC Name\" attack.","ecosystems":[],"exploits":{"exploitdb":3,"first_seen":"2006-11-30","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2006-11-30","kind":"exploitdb","ref":"2870","stars":null,"title":"VUPlayer 2.44 - '.m3u' UNC Name Buffer Overflow (Metasploit)"},{"date":"2006-11-30","kind":"exploitdb","ref":"2872","stars":null,"title":"VUPlayer 2.44 - '.m3u' UNC Name Buffer Overflow"},{"date":"2009-08-18","kind":"metasploit","ref":"exploit/windows/fileformat/vuplayer_m3u","stars":null,"title":"VUPlayer M3U Buffer Overflow"},{"date":"2010-11-11","kind":"exploitdb","ref":"16617","stars":null,"title":"VUPlayer - '.m3u' Local Buffer Overflow (Metasploit)"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2006-6251","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":7,"next":{"headline":"Denial of service in n/a","id":"CVE-2006-6252"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2006-6250"},"products":["n/a"],"published":"2006-12-04","related":[{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2009-0174","kev_date_added":null,"published":"2009-01-20"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2009-0181","kev_date_added":null,"published":"2009-01-20"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2009-0182","kev_date_added":null,"published":"2009-01-20"}],"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious M3U file in VUPlayer.","url":"https://insights.sbomify.com/CVE-2006-6251/"}