CVE-2016-1675

UnknownEPSS 1.53%

Last modified

CVE-2016-1675 is a vulnerability of currently unknown severity. Blink, as used in Google Chrome before 51.0.2704.63, allows remote attackers to bypass the Same Origin Policy by leveraging the mishandling of Document reattachment during destruction, related to FrameLoader.cpp and LocalFrame.cpp.. EPSS estimates a 1.53% chance of exploitation in the next 30 days.

Description

Blink, as used in Google Chrome before 51.0.2704.63, allows remote attackers to bypass the Same Origin Policy by leveraging the mishandling of Document reattachment during destruction, related to FrameLoader.cpp and LocalFrame.cpp.

Metrics

EPSS Probability
1.53%

71.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
CanonicalUbuntu Linux14.04
CanonicalUbuntu Linux15.10
CanonicalUbuntu Linux16.04
DebianDebian Linux8.0
OpensuseLeap42.1
OpensuseOpensuse13.2
RedhatEnterprise Linux Desktop6.0
RedhatEnterprise Linux Server6.0
RedhatEnterprise Linux Workstation6.0
SuseLinux Enterprise12.0
GoogleChrome<= 50.0.2661.102

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-1675?
Blink, as used in Google Chrome before 51.0.2704.63, allows remote attackers to bypass the Same Origin Policy by leveraging the mishandling of Document reattachment during destruction, related to FrameLoader.cpp and LocalFrame.cpp.
How severe is CVE-2016-1675?
Severity scoring for CVE-2016-1675 is pending analysis. The EPSS model estimates a 1.53% probability of exploitation in the next 30 days.
How do I fix CVE-2016-1675?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-1675?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST