{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2018-8231 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8231 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8231 is a high-severity memory corruption vulnerability in Microsoft Windows 10, published on 14 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-8231 and fix it if it is affected.\n\nWhat it is: CVE-2018-8231 is a high-severity memory corruption vulnerability in Microsoft Windows 10, published on 14 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-8231 in the wild and no public exploit code.\n\nAffected product: Microsoft Windows 10. 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-8231/ (Markdown: https://insights.sbomify.com/CVE-2018-8231/index.md)","id":"CVE-2018-8231","markdown":"https://insights.sbomify.com/CVE-2018-8231/index.md","name":"CVE-2018-8231","record":{"aliases":["GHSA-hmwc-h5cg-w686"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Windows HTTP Stack","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by exploiting improper memory handling in the Windows HTTP Protocol Stack.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"windows_10","vendor":"microsoft"},{"product":"windows_server_1803","vendor":"microsoft"},{"product":"windows_server_2016","vendor":"microsoft"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"A remote code execution vulnerability exists when HTTP Protocol Stack (Http.sys) improperly handles objects in memory, aka \"HTTP Protocol Stack Remote Code Execution Vulnerability.\" This affects Windows Server 2016, Windows 10, Windows 10 Servers.","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":"Memory corruption in Windows 10","id":"CVE-2018-8231","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:windows_10","products":["microsoft:windows_10","microsoft:windows_server_2016"],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in Microsoft Visual Studio","id":"CVE-2018-8232"},"packages":[],"prev":{"headline":"ChakraCore RCE Vulnerability","id":"CVE-2018-8229"},"products":["Windows 10","Windows 10 Servers","Windows Server 2016"],"published":"2018-06-14","related":[{"cvss_score":8.8,"headline":"Microsoft Windows Adobe Type Manager Library Remote Code Execution","id":"CVE-2015-2426","kev_date_added":"2022-03-28","published":"2015-07-20"},{"cvss_score":6.6,"headline":"Microsoft Windows Mount Manager Privilege Escalation","id":"CVE-2015-1769","kev_date_added":"2022-05-25","published":"2015-08-15"},{"cvss_score":10,"headline":"Windows Hard Link Elevation of Privilege Vulnerability","id":"CVE-2020-1467","kev_date_added":null,"published":"2020-08-17"},{"cvss_score":9.9,"headline":"Windows TCP/IP Remote Code Execution Vulnerability","id":"CVE-2021-26424","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":9.9,"headline":"Windows Hyper-V Remote Code Execution Vulnerability","id":"CVE-2021-28476","kev_date_added":null,"published":"2021-05-11"},{"cvss_score":9.9,"headline":"Windows Hyper-V Remote Code Execution Vulnerability","id":"CVE-2021-26867","kev_date_added":null,"published":"2021-03-11"},{"cvss_score":9.9,"headline":"Security feature bypass in Windows","id":"CVE-2019-1384","kev_date_added":null,"published":"2019-11-12"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Microsoft"]},"summary":"Remote attackers can execute arbitrary code by exploiting improper memory handling in the Windows HTTP Protocol Stack.","url":"https://insights.sbomify.com/CVE-2018-8231/"}