CVE-2016-1636 Security feature bypass in n/a

Critical 9.8 Published Updated

Remote attackers can bypass Subresource Integrity protections in Google Chrome by triggering duplicate resource loads, undermining script integrity checks.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2016-1636?

CVE-2016-1636 is a critical vulnerability in Google Chrome, published on 6 Mar 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

The PendingScript::notifyFinished function in WebKit/Source/core/dom/PendingScript.cpp in Google Chrome before 49.0.2623.75 relies on memory-cache information about integrity-check occurrences instead of integrity-check successes, which allows remote attackers to bypass the Subresource Integrity (aka SRI) protection mechanism by triggering two loads of the same resource.

Weakness: CWE-264

Which versions are affected by CVE-2016-1636?

It affects 1 product.

Products include Google Chrome.

How do I fix CVE-2016-1636?

Upgrade to a fixed version.

Is CVE-2016-1636 being exploited?

There is no known exploitation of CVE-2016-1636 in the wild and no public exploit code.

All Google Chrome vulnerabilities

Sources

Also known as GHSA-ffvj-r26r-x2p8, UBUNTU-CVE-2016-1636.

Is CVE-2016-1636 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free