CVE-2018-0860
HIGHCVE-2018-0860 is a high-severity (CVSS 7.5) Out-of-bounds Write vulnerability in microsoft edge. 4 public exploit references exist, so weaponization risk is real. O3 Security detects and blocks CVE-2018-0860 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.
Microsoft Edge and ChakraCore in Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows remote code execution, due to how the scripting engine handles objects…
Description
Microsoft Edge and ChakraCore in Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows remote code execution, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2018-0834, CVE-2018-0835, CVE-2018-0836, CVE-2018-0837, CVE-2018-0838, CVE-2018-0840, CVE-2018-0856, CVE-2018-0857, CVE-2018-0858, CVE-2018-0859, CVE-2018-0861, and CVE-2018-0866.
Affected Products
edgemicrosoftResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Microsoft Edge Chakra JIT - Memory Corruption
by Google Security Research · Feb 15, 2018
Detection & mitigation playbook
Vendor / applianceDetect
Inventory every microsoft edge deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2018-0860 yet — track the microsoft edge advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2018-0860 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.
Tailored to CVE-2018-0860. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2018-0860 being exploited in your environment?
O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2018-0860 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.