CVE-2016-5150

UnknownEPSS 1.27%

Last modified

CVE-2016-5150 is a vulnerability of currently unknown severity. WebKit/Source/bindings/modules/v8/V8BindingForModules.cpp in Blink, as used in Google Chrome before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on Linux, has an Indexed Database (aka IndexedDB) API implementation that does not properly restrict key-path evaluation, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted JavaScript code that leverages certain side effects.. EPSS estimates a 1.27% chance of exploitation in the next 30 days.

Description

WebKit/Source/bindings/modules/v8/V8BindingForModules.cpp in Blink, as used in Google Chrome before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on Linux, has an Indexed Database (aka IndexedDB) API implementation that does not properly restrict key-path evaluation, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted JavaScript code that leverages certain side effects.

Metrics

EPSS Probability
1.27%

66.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
OpensuseLeap42.1
GoogleChrome<= 52.0.2743.116

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-5150?
WebKit/Source/bindings/modules/v8/V8BindingForModules.cpp in Blink, as used in Google Chrome before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on Linux, has an Indexed Database (aka IndexedDB) API implementation that does not properly restrict key-path evaluation, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted JavaScript code that leverages certain side effects.
How severe is CVE-2016-5150?
Severity scoring for CVE-2016-5150 is pending analysis. The EPSS model estimates a 1.27% probability of exploitation in the next 30 days.
How do I fix CVE-2016-5150?
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-5150?

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

Scan your code now

Source: NVD / NIST