Skip to content
Fencer Intel
medium 6.5

CVE-2016-10506 json

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…

published 2017-08-30 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-1688

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.3%
EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

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.

Patch / fix

  • openjpeg2 Debian 14, Debian 13, Debian 12 2.2.0-1

debian advisories DEBIAN-CVE-2016-10506

  • openjpeg2 Ubuntu 16.04 LTS 2.1.2-1.1+deb9u5build0.16.04.1
  • openjpeg Ubuntu Pro 16.04 LTS 1:1.5.2-3.1ubuntu0.1~esm2

ubuntu advisories UBUNTU-CVE-2016-10506

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-10506 updated cvss 3.3

openjpeg: Division by zero in functions opj_pi_next_cprl, opj_pi_next_pcrl, and opj_pi_next_rpcl in pi.c

  • Red Hat Enterprise Linux 6 openjpeg, openjpeg-libs Red Hat Enterprise Linux 7 openjpeg, openjpeg-libs
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.32% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.