{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-0499 exists.","fix":"No fix has been published for CVE-2011-0499 yet. Limit exposure of the affected software until one is available.","what":"CVE-2011-0499 is a critical memory corruption vulnerability in n/a, published on 20 Jan 2011. 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-2011-0499 and fix it if it is affected.\n\nWhat it is: CVE-2011-0499 is a critical memory corruption vulnerability in n/a, published on 20 Jan 2011. 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-2011-0499 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-2011-0499/ (Markdown: https://insights.sbomify.com/CVE-2011-0499/index.md)","id":"CVE-2011-0499","markdown":"https://insights.sbomify.com/CVE-2011-0499/index.md","name":"CVE-2011-0499","record":{"aliases":["GHSA-9mrw-5cmq-64wh"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"VideoSpirit video editor","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious VideoSpirit project file with a long name attribute.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"videospirit_lite","vendor":"verytools"},{"product":"videospirit_pro","vendor":"verytools"}],"cvss":{"score":9.3,"severity":"critical","source":"nvd","vector":"AV:N/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Buffer overflow in VideoSpirit Pro 1.6.8.1 and possibly earlier versions, and VideoSpirit Lite 1.4.0.1 and possibly other versions, allows user-assisted remote attackers to execute arbitrary code via a VideoSpirit project (.visprj) file containing a valitem element with a long \"name\" attribute.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2011-01-08","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2011-01-08","kind":"exploitdb","ref":"15936","stars":null,"title":"VeryTools VideoSpirit Pro 1.68 - Local Buffer Overflow"},{"date":"2011-04-11","kind":"exploitdb","ref":"17153","stars":null,"title":"VeryTools VideoSpirit Pro 1.70 - '.visprj' Local Buffer Overflow (Metasploit)"},{"date":"2011-04-11","kind":"metasploit","ref":"exploit/windows/fileformat/videospirit_visprj","stars":null,"title":"VeryTools Video Spirit Pro"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2011-0499","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2011"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2011-0500"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2011-0498"},"products":["n/a"],"published":"2011-01-20","related":[{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2011-0500","kev_date_added":null,"published":"2011-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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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-06","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious VideoSpirit project file with a long name attribute.","url":"https://insights.sbomify.com/CVE-2011-0499/"}