{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2018-8313 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8313 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8313 is a high-severity vulnerability in Microsoft Windows 10, 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-8313 and fix it if it is affected.\n\nWhat it is: CVE-2018-8313 is a high-severity vulnerability in Microsoft Windows 10, 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-8313 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-8313/ (Markdown: https://insights.sbomify.com/CVE-2018-8313/index.md)","id":"CVE-2018-8313","markdown":"https://insights.sbomify.com/CVE-2018-8313/index.md","name":"CVE-2018-8313","record":{"aliases":["GHSA-4rv5-hh7f-94pj"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows OS","requires_auth":"low_privilege","summary":"Attackers can exploit a Windows Kernel API permission enforcement flaw to elevate privileges on affected Windows systems.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"windows_10","vendor":"microsoft"},{"product":"windows_8.1","vendor":"microsoft"},{"product":"windows_rt_8.1","vendor":"microsoft"},{"product":"windows_server_2012","vendor":"microsoft"},{"product":"windows_server_2016","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":[],"description":"An elevation of privilege vulnerability exists in the way that the Windows Kernel API enforces permissions, aka \"Windows Elevation of Privilege Vulnerability.\" This affects Windows Server 2012 R2, Windows RT 8.1, Windows Server 2012, Windows Server 2016, Windows 8.1, Windows 10, Windows 10 Servers. This CVE ID is unique from CVE-2018-8314.","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":"Privilege escalation in Windows 10","id":"CVE-2018-8313","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:windows_10","products":["microsoft:windows_10","microsoft:windows_8.1","microsoft:windows_rt_8.1","microsoft:windows_server_2012","microsoft:windows_server_2016"],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in Windows 10","id":"CVE-2018-8314"},"packages":[],"prev":{"headline":"Memory corruption in Microsoft Access","id":"CVE-2018-8312"},"products":["Windows 10","Windows 10 Servers","Windows 8.1","Windows RT 8.1","Windows Server 2012","Windows Server 2012 R2","Windows Server 2016"],"published":"2018-07-11","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":"Attackers can exploit a Windows Kernel API permission enforcement flaw to elevate privileges on affected Windows systems.","url":"https://insights.sbomify.com/CVE-2018-8313/"}