{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4494 exists.","fix":"No fix has been published for CVE-2006-4494 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-4494 is a high-severity memory corruption vulnerability in Microsoft Visual Studio, published on 31 Aug 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-4494 and fix it if it is affected.\n\nWhat it is: CVE-2006-4494 is a high-severity memory corruption vulnerability in Microsoft Visual Studio, published on 31 Aug 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-4494 exists.\n\nAffected product: Microsoft Visual Studio. 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-4494/ (Markdown: https://insights.sbomify.com/CVE-2006-4494/index.md)","id":"CVE-2006-4494","markdown":"https://insights.sbomify.com/CVE-2006-4494/index.md","name":"CVE-2006-4494","record":{"aliases":["GHSA-j5fh-hp66-hvgw"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Visual Studio ActiveX","requires_auth":"none","summary":"Remote attackers can trigger memory corruption and potentially execute code via malicious ActiveX objects in Internet Explorer.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"visual_studio","vendor":"microsoft"}],"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":"Microsoft Visual Studio 6.0 allows remote attackers to cause a denial of service (memory corruption) and possibly execute arbitrary code by instantiating certain Visual Studio 6.0 ActiveX COM Objects in Internet Explorer, including (1) tcprops.dll, (2) fp30wec.dll, (3) mdt2db.dll, (4) mdt2qd.dll, and (5) vi30aut.dll.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-08-08","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-08-08","kind":"exploitdb","ref":"28401","stars":null,"title":"Microsoft Internet Explorer 6 - Visual Studio COM Object Instantiation Denial of Service"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2006-4494","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio","products":["microsoft:visual_studio"],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-4495"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2006-4493"},"products":["n/a"],"published":"2006-08-31","related":[{"cvss_score":8.8,"headline":"Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2025-49739","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35777","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35825","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35826","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35827","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":7.8,"headline":"Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2024-20656","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":7.8,"headline":"Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability","id":"CVE-2021-28313","kev_date_added":null,"published":"2021-04-13"}],"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":"Remote attackers can trigger memory corruption and potentially execute code via malicious ActiveX objects in Internet Explorer.","url":"https://insights.sbomify.com/CVE-2006-4494/"}