{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4789 exists.","fix":"No fix has been published for CVE-2006-4789 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-4789 is a medium-severity memory corruption vulnerability in n/a, published on 14 Sep 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2006-4789 and fix it if it is affected.\n\nWhat it is: CVE-2006-4789 is a medium-severity memory corruption vulnerability in n/a, published on 14 Sep 2006. It can only be exploited from the same machine or local network, 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-4789 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-4789/ (Markdown: https://insights.sbomify.com/CVE-2006-4789/index.md)","id":"CVE-2006-4789","markdown":"https://insights.sbomify.com/CVE-2006-4789/index.md","name":"CVE-2006-4789","record":{"aliases":["GHSA-vmwp-3hqh-xhpf"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Open Movie Editor","requires_auth":"none","summary":"Local attackers can execute arbitrary code or crash the system by tricking a user into opening a malicious project file with a long name.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"open_movie_editor","vendor":"open_movie_editor"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Buffer overflow in Open Movie Editor 0.0.20060901 allows local users to cause a denial of service (system crash) or execute arbitrary code via a long project name in an open_movie_editor_project XML tag.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-09-09","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-09-09","kind":"exploitdb","ref":"2338","stars":null,"title":"openmovieeditor 0.0.20060901 - 'name' Local Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2006-4789","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2006-4790"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2006-4788"},"products":["n/a"],"published":"2006-09-14","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)"},{"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":"Local attackers can execute arbitrary code or crash the system by tricking a user into opening a malicious project file with a long name.","url":"https://insights.sbomify.com/CVE-2006-4789/"}