Vulnerabilities · 2016 · Google
CVE-2016-1684
Google Chrome vulnerability
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.
Affected products
Chrome, Libxslt. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Chrome runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html
- lists.apple.com/archives/security-announce/2016/Jul/msg00000.html
- lists.apple.com/archives/security-announce/2016/Jul/msg00001.html
- lists.apple.com/archives/security-announce/2016/Jul/msg00002.html
- lists.apple.com/archives/security-announce/2016/Jul/msg00003.html
- lists.apple.com/archives/security-announce/2016/Jul/msg00005.html
- lists.opensuse.org/opensuse-security-announce/2016-05/msg00062.html
- lists.opensuse.org/opensuse-security-announce/2016-05/msg00063.html
- nvd.nist.gov/vuln/detail/CVE-2016-1684
- cve.org/CVERecord?id=CVE-2016-1684
More vulnerabilities in Google products
CVE-2026-28615CVE-2026-28587CVE-2026-28576CVE-2026-28575CVE-2026-20418CVE-2026-20417CVE-2026-20415CVE-2026-20414All 12,443
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.