Is CVE-2016-5222 exploited in the wild?

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

How severe is CVE-2016-5222?

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

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

It is attacked over the network, in a web application.

Am I affected by CVE-2016-5222?

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-5222: Google Chrome address spoofing in Omnibox

Q: Which products and versions are affected?

Google Chromium < 55.0.2883.75.

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

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

It is attacked over the network, in a web application.

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

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

A vulnerability in Google Chrome's address bar (Omnibox) could allow a malicious website to display a fake web address to the user. This type of spoofing is often used in phishing attacks to trick users into believing they are on a legitimate site, such as a bank or email provider, when they are actually on a site controlled by an attacker. This could lead to the theft of login credentials or other sensitive personal information.

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

Quick answers

Is CVE-2016-5222 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5222 being exploited in the wild.
How severe is CVE-2016-5222?: 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-5222?: 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-5222 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2016-5222?: 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 Omnibox component due to improper input validation of invalid URLs. By enticing a user to visit a specially crafted HTML page, a remote attacker can manipulate the displayed URL in the address bar without navigating to that actual location. This flaw stems from incorrect handling of malformed URL strings, which fails to trigger appropriate security UI indicators or reverts to an incorrect state. The vulnerability was patched 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: 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.