Is CVE-2016-5209 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-5209 being exploited in the wild.

How severe is CVE-2016-5209?

High severity, with a CVSS score of 8.8, published 19 January 2017.

Which products and versions are affected?

Google Chrome for Android prior to 55.0.2883.84; Google Chromium prior to 55.0.2883.75.

Is there a fix for CVE-2016-5209?

A patch was published on 2016-12-01: Chrome Stable Channel Update for Desktop released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2016-5209 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2016-5209?

Check whether you run Google Chrome, Google Chrome for Android or Google Chromium at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2016-5209: Google Chrome bad casting in Blink bitmap manipulation

CVE-2016-5209 · Severity: high · CVSS 8.8 · Published 2017-01-19

A vulnerability in Google Chrome's web rendering engine could allow an attacker to compromise a user's computer if they visit a malicious website. This issue stems from how the browser handles images and could lead to a complete system takeover or the theft of sensitive data. Users are protected by updating to the latest version of the browser.

Technologies: Google Chrome, Google Chrome for Android, Google Chromium. Vendors: Google.

Quick answers

Is CVE-2016-5209 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5209 being exploited in the wild.
How severe is CVE-2016-5209?: High severity, with a CVSS score of 8.8, published 19 January 2017.
Which products and versions are affected?: Google Chrome for Android prior to 55.0.2883.84; Google Chromium prior to 55.0.2883.75.
Is there a fix for CVE-2016-5209?: A patch was published on 2016-12-01: Chrome Stable Channel Update for Desktop released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-5209 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-5209?: Check whether you run Google Chrome, Google Chrome for Android or Google Chromium at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A bad casting vulnerability exists in the bitmap manipulation component of the Blink rendering engine (part of Chromium/Google Chrome). The flaw is triggered when the browser processes specially crafted HTML content, leading to an out-of-bounds write (CWE-787) and subsequent heap corruption. A remote, unauthenticated attacker can exploit this by enticing a user to visit a malicious webpage. Successful exploitation could result in arbitrary code execution within the context of the browser process. The issue was addressed in Chrome version 55.0.2883.75 for desktop and 55.0.2883.84 for Android.

Affected products

Google Chrome prior to 55.0.2883.75
Google Chrome for Android prior to 55.0.2883.84
Google Chromium prior to 55.0.2883.75

Timeline

2016-12-01: patched: Chrome Stable Channel Update for Desktop released
2016-12-05: advisory: Gentoo Linux security advisory published
2016-12-07: advisory: Red Hat security advisory published
2017-01-19: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.