| Reporter | Title | Published | Views | Family All 16 |
|---|---|---|---|---|
| MS Edge CMarkup::EnsureDeleteCFState Use-After-Free Vulnerability | 2 Dec 201600:00 | – | zdt | |
| Microsoft Edge browser vulnerability, which allows a hacker to trigger a service failure or execute arbitrary code | 28 Jan 201600:00 | – | bdu_fstec | |
| CVE-2015-6168 | 6 Dec 201600:00 | – | circl | |
| Microsoft Edge CAttrArray Out-of-Bounds Read Remote Code Execution Vulnerability | 9 Dec 201500:00 | – | cnvd | |
| Microsoft Edge Memory Corruption (MS15-125: CVE-2015-6168) | 8 Dec 201500:00 | – | checkpoint_advisories | |
| CVE-2015-6168 | 9 Dec 201511:00 | – | cve | |
| CVE-2015-6168 | 9 Dec 201511:00 | – | cvelist | |
| MS15-125: Cumulative Security Update for Microsoft Edge: December 8, 2015 | 8 Dec 201500:00 | – | mskb | |
| KLA10720 Multiple vulnerabilities in Microsoft Internet Explorer & Edge | 8 Dec 201500:00 | – | kaspersky | |
| CVE-2015-6168 | 9 Dec 201511:59 | – | nvd |
Source: http://blog.skylined.nl/20161201001.html
Synopsis
A specially crafted web-page can trigger a memory corruption vulnerability in Microsoft Edge. I did not investigate this vulnerability thoroughly, so I cannot speculate on the potential impact or exploitability.
Known affected software and attack vectors
Microsoft Edge 11.0.10240.16384
An attacker would need to get a target user to open a specially crafted web-page. Disabling JavaScript does not prevent an attacker from triggering the vulnerable code path.
Repro:
/<style>:first-letter{word-spacing:9
Variation:
x<style>:first-letter{background-position:inherit
Description
At the time this issue was first discovered, MemGC was just introduced, and I had not yet fully appreciated what an impact it would have on mitigating use-after-free bugs. Despite MemGC being enabled in Microsoft Edge by default, this issue appeared to me to have been a use-after-free vulnerability. However, both Microsoft and ZDI (whom I sold the vulnerability to) describes it as a memory corruption vulnerability, so it's probably more complex than I assumed.
At the time, I did not consider this vulnerability to be of great interest, as there was no immediately obvious way of controlling the vulnerability in order to exploit it. So, I did not do any further investigation into the root cause and, if this was indeed a use-after-free, how come MemGC did not mitigate it? In hindsight, it would have been a good idea to investigate the root cause, as any use-after-free that is not mitigated by MemGC might provide hints on how to find more vulnerabilities that bypass it.
Time-line
August 2015: This vulnerability was found through fuzzing.
August 2015: This vulnerability was submitted to ZDI.
December 2015: Microsoft addresses this vulnerability in MS15-125.
December 2016: Details of this vulnerability are released.
# 0day.today [2018-01-03] #Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation