Vulnerability in Google Chrome

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 7.5 (High). Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.018 (78.8th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 79th percentile — 78.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2016-1684: held from 0.018 to 0.018.

EPSS over last 30 days · oldest: 0.018 · newest: 0.018 · change: 0.000

Affected products

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2016-1684?
CVE-2016-1684 is a high-severity vulnerability in Google Chrome. CVSS score: 7.5/10. Published 2016-06-05.
How severe is CVE-2016-1684?
High severity. CVSS v3 base score is 7.5 out of 10.
Is CVE-2016-1684 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.