CVE-2016-1651: Infoleak
First published: Mon Apr 18 2016(Updated: )
fxcodec/codec/fx_codec_jpx_opj.cpp in PDFium, as used in Google Chrome before 50.0.2661.75, does not properly implement the sycc420_to_rgb and sycc422_to_rgb functions, which allows remote attackers to obtain sensitive information from process memory or cause a denial of service (out-of-bounds read) via crafted JPEG 2000 data in a PDF document.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome | <=49.0.2623.112 | |
| Debian Linux | =8.0 | |
| SUSE Linux | =42.1 | |
| SUSE Linux Enterprise Server | =12.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html
- http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00040.html
- http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00041.html
- http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00049.html
- http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00050.html
- http://rhn.redhat.com/errata/RHSA-2016-0638.html
- http://www.debian.org/security/2016/dsa-3549
- http://zerodayinitiative.com/advisories/ZDI-16-243/
- https://codereview.chromium.org/1837383011
- https://crbug.com/591785
- https://security.gentoo.org/glsa/201605-02
Frequently Asked Questions
What is the severity of CVE-2016-1651?
CVE-2016-1651 is rated as a medium severity vulnerability due to potential information disclosure and denial of service risks.
How do I fix CVE-2016-1651?
To fix CVE-2016-1651, you should update Google Chrome to version 50.0.2661.75 or newer.
What types of systems are affected by CVE-2016-1651?
CVE-2016-1651 affects Google Chrome versions prior to 50.0.2661.75, as well as certain Debian and SUSE Linux distributions.
Can CVE-2016-1651 be exploited remotely?
Yes, CVE-2016-1651 can be exploited by remote attackers to read sensitive information from process memory.
Is there a known workaround for CVE-2016-1651?
There are no known workarounds for CVE-2016-1651; the best mitigation is to apply the necessary updates.
- agent/type
- agent/references
- agent/author
- agent/severity
- agent/weakness
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/google
- canonical/google chrome
- version/google chrome/49.0.2623.112
- vendor/debian
- canonical/debian linux
- version/debian linux/8.0
- vendor/opensuse
- canonical/suse linux
- version/suse linux/42.1
- vendor/suse
- canonical/suse linux enterprise server
- version/suse linux enterprise server/12.0