{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-8232 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8232 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8232 is a high-severity code injection vulnerability in Microsoft Visual Studio 2017, published on 11 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-8232 and fix it if it is affected.\n\nWhat it is: CVE-2018-8232 is a high-severity code injection vulnerability in Microsoft Visual Studio 2017, published on 11 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-8232 in the wild and no public exploit code.\n\nAffected product: Microsoft Visual Studio 2017. 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-2018-8232/ (Markdown: https://insights.sbomify.com/CVE-2018-8232/index.md)","id":"CVE-2018-8232","markdown":"https://insights.sbomify.com/CVE-2018-8232/index.md","name":"CVE-2018-8232","record":{"aliases":["GHSA-7rhj-mfh9-5577"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Visual Studio Assembler","requires_auth":"low_privilege","summary":"An attacker can execute arbitrary code by exploiting improper validation in the Microsoft Macro Assembler within Visual Studio.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio_2017","vendor":"microsoft"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A Tampering vulnerability exists when Microsoft Macro Assembler improperly validates code, aka \"Microsoft Macro Assembler Tampering Vulnerability.\" This affects Microsoft Visual Studio.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Code injection in Microsoft Visual Studio","id":"CVE-2018-8232","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio_2017","products":["microsoft:visual_studio_2017"],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in Windows 10","id":"CVE-2018-8233"},"packages":[],"prev":{"headline":"Memory corruption in Windows 10","id":"CVE-2018-8231"},"products":["Microsoft Visual Studio"],"published":"2018-07-11","related":[{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2025-21178","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1349","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1350","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1352","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1354","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":7.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2023-28296","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":7.8,"headline":"Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2023-21566","kev_date_added":null,"published":"2023-02-14"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Microsoft"]},"summary":"An attacker can execute arbitrary code by exploiting improper validation in the Microsoft Macro Assembler within Visual Studio.","url":"https://insights.sbomify.com/CVE-2018-8232/"}