CVE-2016-1645
What it is
Multiple integer signedness errors in the opj_j2k_update_image_data function in j2k.c in OpenJPEG, as used in PDFium in Google Chrome before 49.0.2623.87, allow remote attackers to cause a denial of service (incorrect cast and out-of-bounds write) or possibly have unspecified other impact via crafted JPEG 2000 data.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 2.0% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 2.0% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 2.0% · EPSS, next 30 days
- Weakness
- CWE-119 · Buffer errors
- Record status
- Modified
Affected
- Google Chrome ≤ 49.0.2623.75
- Debian Linux 8.0
- Opensuse Leap 42.1
- Opensuse 13.1
- Opensuse 13.2
- Opensuse Suse Linux Enterprise Server 12.0
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2016-1645.md and follow it. Check whether this project is affected by CVE-2016-1645. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_8.html
- http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00066.html
- http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00067.html
- http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00073.html
- http://www.debian.org/security/2016/dsa-3513
- http://www.securityfocus.com/bid/84224
- http://www.securitytracker.com/id/1035259
- http://www.zerodayinitiative.com/advisories/ZDI-16-197/
- https://code.google.com/p/chromium/issues/detail?id=587227
- https://pdfium.googlesource.com/pdfium/+/c145aeb2bf13ac408fc3e8233acca43d4251bbdc
- http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_8.html
- http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00066.html
- http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00067.html
- http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00073.html
- http://www.debian.org/security/2016/dsa-3513
- http://www.securityfocus.com/bid/84224
- http://www.securitytracker.com/id/1035259
- http://www.zerodayinitiative.com/advisories/ZDI-16-197/
- https://code.google.com/p/chromium/issues/detail?id=587227
- https://pdfium.googlesource.com/pdfium/+/c145aeb2bf13ac408fc3e8233acca43d4251bbdc