dbcve.org
OpenjpegApplication · Uclouvain

CVE-2023-39329

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in OpenJPEG. A resource exhaustion can occur in the opj_t1_decode_cblks function in tcd.c through a crafted image file, causing a denial of service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OpenJPEG's opj_t1_decode_cblks function in tcd.c suffers from resource exhaustion when processing crafted JPEG2000 image files. This allows attackers to cause a denial of service by providing specially constructed image data that triggers excessive memory allocation or CPU consumption during tile codeblock decoding.

MitigationUpdate OpenJPEG to the patched version. If updates are unavailable, implement input validation and resource limits (memory caps, timeout constraints) on image processing operations, and scan/filter untrusted JPEG2000 files before processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenjpegApplication
Affected:= 2.0all versions= 2.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if OpenJPEG is installed
    Run 'opj_version' or check package manager: 'dpkg -l | grep openjpeg' (Debian), 'rpm -qa | grep openjpeg' (RHEL), or 'brew list openjpeg' (macOS)
    Affected if OpenJPEG is not found on the system
  2. Identify the installed OpenJPEG version
    Run 'opj_version' output, or check library: 'ldd /path/to/binary | grep openjpeg' and then check the actual library version from the file path, or review packaging metadata
    Affected if Version is 2.0.x (any 2.0.x release) or exactly 2.5.0
  3. Confirm application uses OpenJPEG for JPEG2000 decoding
    Inspect running services that process images: check application dependencies, look for openjpeg libraries loaded in memory via 'lsof' on image processing processes, or review application documentation for JPEG2000 support
    Affected if Applications process JPEG2000 files using OpenJPEG library
  4. Determine exposure to untrusted JPEG2000 input
    Audit image upload/processing workflows: check web applications, document converters, or imaging tools that accept user-supplied files; review file type handling configuration to see if .jp2, .j2k, .jpx extensions are accepted
    Affected if Untrusted or user-uploaded JPEG2000 files can reach OpenJPEG for decoding

You are affected if OpenJPEG version 2.0.x or 2.5.0 is installed and processes untrusted or user-supplied JPEG2000 image files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update OpenJPEG to the patched version. If updates are unavailable, implement input validation and resource limits (memory caps, timeout constraints) on image processing operations, and scan/filter untrusted JPEG2000 files before processing.

Recommended fix Moderate confidence

OpenJPEG >= 2.5.1 or >= 2.4.18 (any stable release after 2.5.0)

  1. 1. Identify the current OpenJPEG version installed in your system using package manager or checking library version
  2. 2. For RHEL/CentOS systems: Run 'yum update openjpeg2' or 'dnf update openjpeg2' to apply available security updates
  3. 3. For Debian/Ubuntu systems: Run 'apt-get update && apt-get install libopenjp2-7' to get the latest packaged version
  4. 4. For source builds: Download OpenJPEG 2.5.1 or later from the official GitHub repository (https://github.com/uclouvain/openjpeg)
  5. 5. Rebuild and reinstall the library: cmake -DCMAKE_BUILD_TYPE=Release .. && make && make install
  6. 6. Restart any services or applications that use OpenJPEG to ensure they load the updated library
  7. 7. Verify the fix by checking the updated version and testing with the previously vulnerable image processing
Caveat Minimal risk - patch release maintains API/ABI compatibility; verify any custom code that directly links to internal symbols not part of public API

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openjpeg Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39329 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data