CVE-2016-1684

UnknownEPSS 1.91%

Last modified

CVE-2016-1684 is a vulnerability of currently unknown severity. numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service (integer overflow or resource consumption) or possibly have unspecified other impact via a crafted document.. EPSS estimates a 1.91% chance of exploitation in the next 30 days.

Description

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service (integer overflow or resource consumption) or possibly have unspecified other impact via a crafted document.

Metrics

EPSS Probability
1.91%

77.2th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
GoogleChrome<= 50.0.2661.102
XmlsoftLibxslt<= 1.1.28

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-1684?
numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service (integer overflow or resource consumption) or possibly have unspecified other impact via a crafted document.
How severe is CVE-2016-1684?
Severity scoring for CVE-2016-1684 is pending analysis. The EPSS model estimates a 1.91% probability of exploitation in the next 30 days.
How do I fix CVE-2016-1684?
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-1684?

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

Scan your code now

Source: NVD / NIST