A vulnerability, which was classified as critical, was found in Google Chrome 48.0.2540.0 dev-m (Web Browser). Affected is the function blink::Node. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on confidentiality, integrity, and availability.

The weakness was shared 11/29/2016 by Berend-Jan Wever (SkyLined) as Google Chrome Accessibility blink::Node corruption details as not defined mailinglist post (Bugtraq). The advisory is shared for download at seclists.org. The public release happened without coordination with the vendor. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/12/2019). It is expected to see the exploit prices for this product increasing in the near future. The advisory points out:

A specially crafted web-page can trigger an unknown memory corruption vulnerability in Google Chrome Accessibility code. An attacker can cause code to attempt to execute a method of an object using a vftable, when the pointer to that object is not valid, or the object is not of the expected type. Successful exploitation can lead to arbitrary code execution.

The real existence of this vulnerability is still doubted at the moment.

Upgrading eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. The mailinglist post contains the following remark:

Is is unclear to me why the `blink::Node` instance was corrupted. During analysis, I was having trouble running Google Chrome with Page Heap enabled, which severely limited my ability to reliably crash the application and find out what information on the heap belongs to what object. Then, before I could get my debugging environment fixed, the issue appears to have been fixed, as I was no longer able to reproduce it. Any information on exploitability is therefore based on speculation.

Productinfo

Type

• Web Browser

Vendor

• Google

Name

• Chrome

Version

• 48.0.2540.0 dev-m

License

• free

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion