Openjpeg vulnerabilitiesRanked by how likely they are to be used.

Product20 versions
The short answer

Openjpeg is made by Uclouvain. We track 82 published vulnerabilities in it, across 20 versions. None of them is on the list of flaws known to be exploited today. If you run Openjpeg, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Openjpeg vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Openjpeg's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Openjpeg flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 8.2%

    Heap-based buffer overflow vulnerability in the opj_mqc_byteout function in mqc.c in OpenJPEG before 2.2.0 allows remote attackers to cause a denial of service (application crash) via a crafted bmp file.

    CVSS6.5Published30 Aug 2017
  2. 7.7%

    Multiple heap-based buffer overflows in the j2k_read_sot function in j2k.c in OpenJPEG 1.5 allow remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a crafted (1)...

    CVSS10.0Published18 Jul 2012
  3. 7.1%

    Integer overflow in the opj_pi_create_decode function in pi.c in OpenJPEG allows remote attackers to execute arbitrary code via a crafted JP2 file, which triggers an out-of-bounds read or write.

    CVSS7.8Published21 Sep 2016
  4. 6.2%

    Heap-based buffer overflow in OpenJPEG 1.5.0 and earlier allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a crafted JPEG2000 file.

    CVSS6.8Published5 Sep 2012
  5. 5.7%

    A stack-based buffer overflow was discovered in the pgxtoimage function in bin/jp2/convert.c in OpenJPEG 2.2.0.

    CVSS8.8Published30 Aug 2017
  6. 5.5%

    Multiple heap-based buffer overflows in OpenJPEG 1.3 and earlier might allow remote attackers to execute arbitrary code via unspecified vectors.

    CVSS7.5Published12 Dec 2013
  7. 5.4%

    A size-validation issue was discovered in opj_j2k_write_sot in lib/openjp2/j2k.c in OpenJPEG 2.2.0.

    CVSS8.8Published6 Sep 2017
  8. 5.2%

    OpenJPEG through 2.3.1 has a heap-based buffer overflow in opj_t1_clbl_decode_processor in openjp2/t1.c because of lack of opj_j2k_update_image_dimensions validation.

    CVSS7.5Published13 Jan 2020
  9. 5.2%

    An off-by-one error was discovered in opj_tcd_code_block_enc_allocate_data in lib/openjp2/tcd.c in OpenJPEG 2.2.0.

    CVSS8.8Published5 Sep 2017
  10. 5.1%

    A mishandled zero case was discovered in opj_j2k_set_cinema_parameters in lib/openjp2/j2k.c in OpenJPEG 2.2.0.

    CVSS8.8Published5 Sep 2017
Precursor Intelligence

Running Openjpeg? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 82 published vulnerabilities listed under the name Openjpeg, across 20 versions.

None of Openjpeg's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Openjpeg. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.