Is CVE-2016-5219 exploited in the wild?

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

How severe is CVE-2016-5219?

Medium severity, with a CVSS score of 6.3, published 19 January 2017.

Which products and versions are affected?

Google Chromium < 55.0.2883.75.

Is there a fix for CVE-2016-5219?

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

How is CVE-2016-5219 attacked?

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

Am I affected by CVE-2016-5219?

Check whether you run Google Chrome 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-5219: Google Chrome V8 use after free in heap

Q: Which products and versions are affected?

Google Chromium < 55.0.2883.75.

Q: Is there a fix for CVE-2016-5219?

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

Q: How is CVE-2016-5219 attacked?

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

Q: Am I affected by CVE-2016-5219?

Check whether you run Google Chrome 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-5219 · Severity: medium · CVSS 6.3 · Published 2017-01-19

Google Chrome is a widely used web browser. A security flaw was found in its V8 engine, which handles JavaScript. An attacker could exploit this by tricking a user into visiting a specially crafted website, potentially leading to browser crashes or unauthorized access to information.

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

Quick answers

Is CVE-2016-5219 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5219 being exploited in the wild.
How severe is CVE-2016-5219?: Medium severity, with a CVSS score of 6.3, published 19 January 2017.
Which products and versions are affected?: Google Chromium < 55.0.2883.75.
Is there a fix for CVE-2016-5219?: A patch was published on 2016-12-01: Chrome 55.0.2883.75 released for desktop Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-5219 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-5219?: Check whether you run Google Chrome 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 use-after-free (UAF) vulnerability exists in the V8 JavaScript engine within Google Chrome. The flaw is triggered when the engine incorrectly manages memory objects, allowing a remote attacker to exploit heap corruption. By persuading a user to visit a malicious HTML page, an attacker can trigger the UAF condition. This can lead to a denial-of-service (browser crash) or potentially arbitrary code execution within the context of the browser's sandbox. The issue was resolved in Chrome version 55.0.2883.75 for desktop and 55.0.2883.84 for Android.

Affected products

Google Chrome < 55.0.2883.75 (Desktop); < 55.0.2883.84 (Android)
Google Chromium < 55.0.2883.75

Timeline

2016-12-01: patched: Chrome 55.0.2883.75 released for desktop
2016-12-05: advisory: Gentoo GLSA 201612-11 published
2016-12-07: advisory: Red Hat RHSA-2016:2919 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.