Is CVE-2016-5218 exploited in the wild?

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

How severe is CVE-2016-5218?

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-5218?

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-5218 attacked?

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

Am I affected by CVE-2016-5218?

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-5218: Google Chrome address spoofing in Omnibox via PDF navigation

Q: Which products and versions are affected?

Google Chromium < 55.0.2883.75.

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

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-5218 attacked?

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

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

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

Google Chrome is a widely used web browser. A vulnerability in how the browser handles PDF navigation allowed attackers to temporarily change the address shown in the URL bar (Omnibox). This could be used in phishing attacks to trick users into believing they are on a legitimate website when they are actually on a malicious one.

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

Quick answers

Is CVE-2016-5218 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5218 being exploited in the wild.
How severe is CVE-2016-5218?: 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-5218?: 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-5218 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-5218?: 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 address spoofing vulnerability exists in the Google Chrome extensions API due to improper input validation during PDF navigation. By enticing a user to visit a specially crafted HTML page containing PDF data, a remote attacker can temporarily manipulate the URL displayed in the Omnibox. This flaw allows for sophisticated phishing attacks where the user is presented with a fraudulent URL while viewing attacker-controlled content. The issue was addressed by improving navigation handling within the PDF viewer component. The vulnerability affected Chrome for Desktop (Windows, Mac, Linux) and 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 Linux security advisory issued
2016-12-07: advisory: Red Hat security advisory issued
2017-01-19: disclosed: NVD publication date

References

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