CVE-2016-10506
What it is
Division-by-zero vulnerabilities in the functions opj_pi_next_cprl, opj_pi_next_pcrl, and opj_pi_next_rpcl in pi.c in OpenJPEG before 2.2.0 allow remote attackers to cause a denial of service (application crash) via crafted j2k files.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of service disruption.
- Exploit odds
- 3.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
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: 3.3% in the next 30 days (EPSS).
- Severity: 6.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.3% · EPSS, next 30 days
- Weakness
- CWE-369
- Record status
- Modified
Affected
- Uclouvain Openjpeg ≤ 2.1.2
Attack profile CVSS 3.0 · 6.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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-10506.md and follow it. Check whether this project is affected by CVE-2016-10506. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/uclouvain/openjpeg/commit/d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b
- https://github.com/uclouvain/openjpeg/issues/731
- https://github.com/uclouvain/openjpeg/issues/732
- https://github.com/uclouvain/openjpeg/issues/777
- https://github.com/uclouvain/openjpeg/issues/778
- https://github.com/uclouvain/openjpeg/issues/779
- https://github.com/uclouvain/openjpeg/issues/780
- https://github.com/uclouvain/openjpeg/commit/d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b
- https://github.com/uclouvain/openjpeg/issues/731
- https://github.com/uclouvain/openjpeg/issues/732
References
- http://www.securityfocus.com/bid/100573
- https://github.com/uclouvain/openjpeg/commit/d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b
- https://github.com/uclouvain/openjpeg/issues/731
- https://github.com/uclouvain/openjpeg/issues/732
- https://github.com/uclouvain/openjpeg/issues/777
- https://github.com/uclouvain/openjpeg/issues/778
- https://github.com/uclouvain/openjpeg/issues/779
- https://github.com/uclouvain/openjpeg/issues/780
- https://security.gentoo.org/glsa/201710-26
- http://www.securityfocus.com/bid/100573
- https://github.com/uclouvain/openjpeg/commit/d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b
- https://github.com/uclouvain/openjpeg/issues/731
- https://github.com/uclouvain/openjpeg/issues/732
- https://github.com/uclouvain/openjpeg/issues/777
- https://github.com/uclouvain/openjpeg/issues/778
- https://github.com/uclouvain/openjpeg/issues/779
- https://github.com/uclouvain/openjpeg/issues/780
- https://security.gentoo.org/glsa/201710-26