Is CVE-2016-9650 exploited in the wild?

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

How severe is CVE-2016-9650?

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

Which products and versions are affected?

Google Chromium prior to 55.0.2883.75.

Is there a fix for CVE-2016-9650?

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

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

Am I affected by CVE-2016-9650?

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-9650: Google Chrome Blink no-referrer policy bypass in iframes

CVE-2016-9650 · Severity: medium · CVSS 4.3 · Published 2017-01-19

A vulnerability in the Google Chrome web browser could allow a malicious website to bypass privacy settings intended to hide where a user is visiting from. Specifically, it allows a site to see the 'referrer' information even when a 'no-referrer' policy is in place. This could lead to the unintended disclosure of sensitive URL information to third-party websites.

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

Quick answers

Is CVE-2016-9650 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-9650 being exploited in the wild.
How severe is CVE-2016-9650?: Medium severity, with a CVSS score of 4.3, published 19 January 2017.
Which products and versions are affected?: Google Chromium prior to 55.0.2883.75.
Is there a fix for CVE-2016-9650?: 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-9650 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-9650?: 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 vulnerability exists in the Blink rendering engine within Google Chrome due to improper handling of iframes. A remote attacker can exploit this by enticing a user to visit a specially crafted HTML page, which allows the attacker to bypass the Content Security Policy (CSP) 'no-referrer' directive. This results in the disclosure of referrer information that should have been suppressed. The issue affects Chrome on Mac, Windows, Linux, and Android, and was addressed in version 55.0.2883.75 for desktop and 55.0.2883.84 for Android.

Affected products

Google Chrome prior to 55.0.2883.75 (Desktop); prior to 55.0.2883.84 (Android)
Google Chromium prior to 55.0.2883.75

Timeline

2016-12-01: patched: Chrome 55.0.2883.75 released for desktop
2017-01-19: disclosed: NVD publication date

References

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