Is CVE-2016-5225 exploited in the wild?

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

How severe is CVE-2016-5225?

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

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

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

Am I affected by CVE-2016-5225?

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-5225: Google Chrome CSP bypass in Blink form actions

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

A vulnerability in Google Chrome's web engine allowed websites to bypass security restrictions known as Content Security Policy (CSP). CSP is a security layer that helps detect and mitigate certain types of attacks, including data theft and site defacement. By exploiting this flaw through a specially crafted web page, an attacker could bypass these protections, potentially leading to unauthorized actions on behalf of the user.

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

Quick answers

Is CVE-2016-5225 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5225 being exploited in the wild.
How severe is CVE-2016-5225?: 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-5225?: 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-5225 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2016-5225?: 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 of Google Chrome due to improper handling of form actions. This flaw allows a remote attacker to bypass Content Security Policy (CSP) protections by enticing a user to visit a specially crafted HTML page. The root cause is a data processing error (CWE-19) in how form-related actions are validated against CSP directives. Successful exploitation allows an attacker to circumvent security restrictions that would otherwise prevent unauthorized script execution or data exfiltration. The issue was addressed in Chrome version 55.0.2883.75 for desktop and 55.0.2883.84 for Android.

Affected products

Google Chrome prior to 55.0.2883.75
Google Chrome 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
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.