Vulnerabilities · 2016 · Google
CVE-2016-1628
Google Chrome vulnerability
pi.c in OpenJPEG, as used in PDFium in Google Chrome before 48.0.2564.109, does not validate a certain precision value, which allows remote attackers to execute arbitrary code or cause a denial of service (out-of-bounds read) via a crafted JPEG 2000 image in a PDF document, related to the opj_pi_next_rpcl, opj_pi_next_pcrl, and opj_pi_next_cprl functions.
Affected products
Chrome, Debian Linux. 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/02/stable-channel-update_9.html
- rhn.redhat.com/errata/RHSA-2016-0241.html
- www.debian.org/security/2016/dsa-3486
- www.debian.org/security/2017/dsa-4013
- www.securityfocus.com/bid/83125
- www.securitytracker.com/id/1035183
- www.zerodayinitiative.com/advisories/ZDI-16-172/
- code.google.com/p/chromium/issues/detail?id=571479
- nvd.nist.gov/vuln/detail/CVE-2016-1628
- cve.org/CVERecord?id=CVE-2016-1628
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.