{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0187 exists.","fix":"No fix has been published for CVE-2006-0187 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-0187 is a medium-severity code injection vulnerability in n/a, published on 12 Jan 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-0187 and fix it if it is affected.\n\nWhat it is: CVE-2006-0187 is a medium-severity code injection vulnerability in n/a, published on 12 Jan 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-0187 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-0187/ (Markdown: https://insights.sbomify.com/CVE-2006-0187/index.md)","id":"CVE-2006-0187","markdown":"https://insights.sbomify.com/CVE-2006-0187/index.md","name":"CVE-2006-0187","record":{"aliases":["GHSA-wxv2-7rm9-chw9"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Visual Studio IDE","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening malicious Visual Studio project files due to automatic code execution in control load events.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"visual_studio_.net","vendor":"microsoft"}],"cvss":{"score":5.1,"severity":"medium","source":"nvd","vector":"AV:N/AC:H/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"By design, Microsoft Visual Studio 2005 automatically executes code in the Load event of a user-defined control (UserControl1_Load function), which allows user-assisted attackers to execute arbitrary code by tricking the user into opening a malicious Visual Studio project file.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2006-01-12","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-01-12","kind":"exploitdb","ref":"27072","stars":null,"title":"Microsoft Visual Studio - UserControl Remote Code Execution (1)"},{"date":"2006-01-12","kind":"exploitdb","ref":"27073","stars":null,"title":"Microsoft Visual Studio - UserControl Remote Code Execution (2)"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2006-0187","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2006"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-0188"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-0185"},"products":["n/a"],"published":"2006-01-12","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2007-1512","kev_date_added":null,"published":"2007-03-20"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-0025","kev_date_added":null,"published":"2007-02-13"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2006-4704","kev_date_added":null,"published":"2006-11-01"}],"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":"Attackers can execute arbitrary code by tricking users into opening malicious Visual Studio project files due to automatic code execution in control load events.","url":"https://insights.sbomify.com/CVE-2006-0187/"}