Is CVE-2016-5220 exploited in the wild?

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

How severe is CVE-2016-5220?

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

Which products and versions are affected?

Google Chromium < 55.0.2883.75.

Is there a fix for CVE-2016-5220?

A patch was published on 2016-12-07: Red Hat released security update RHSA-2016:2919 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2016-5220 attacked?

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

Am I affected by CVE-2016-5220?

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-5220: Google Chrome local file disclosure in PDFium

Q: Which products and versions are affected?

Google Chromium < 55.0.2883.75.

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

A patch was published on 2016-12-07: Red Hat released security update RHSA-2016:2919 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2016-5220 attacked?

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

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

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-5220 · Severity: medium · CVSS 6.5 · Published 2017-01-19

Google Chrome's PDF viewer, PDFium, contained a flaw in how it handled navigation within PDF documents. An attacker could exploit this by tricking a user into opening a specially crafted PDF file, which would then allow the attacker to access and read private files stored on the user's computer or device. This could lead to the theft of sensitive personal information or corporate data.

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

Quick answers

Is CVE-2016-5220 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5220 being exploited in the wild.
How severe is CVE-2016-5220?: Medium severity, with a CVSS score of 6.5, published 19 January 2017.
Which products and versions are affected?: Google Chromium < 55.0.2883.75.
Is there a fix for CVE-2016-5220?: A patch was published on 2016-12-07: Red Hat released security update RHSA-2016:2919 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-5220 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-5220?: 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

An information disclosure vulnerability existed in PDFium, the PDF engine used in Google Chrome and Chromium-based browsers. The flaw was rooted in the incorrect handling of navigation events within PDF documents. By enticing a user to open a maliciously crafted PDF, a remote attacker could bypass security boundaries to access and read arbitrary local files on the host system. This vulnerability is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). The issue was resolved in Chrome version 55.0.2883.75 for desktop platforms 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: advisory: Google released Chrome 55.0.2883.75 with security fixes
2016-12-05: advisory: Gentoo released GLSA 201612-11
2016-12-07: patched: Red Hat released security update RHSA-2016:2919
2017-01-19: disclosed: NVD publication date

References

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