dbcve.org
OpenjpegApplication · Uclouvain

CVE-2012-3358

HIGH · 10.0 CVSS v2.0 Published 2012-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
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) tile number or (2) tile length in a JPEG 2000 image file.

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 · high confidence

Heap-based buffer overflow vulnerability in OpenJPEG 1.5's j2k_read_sot function in j2k.c. The function fails to properly validate tile number and tile length values from JPEG 2000 image files before allocating or accessing heap buffers, allowing attackers to overflow allocated buffers with crafted input.

MitigationUpdate OpenJPEG to a patched version that includes proper bounds checking on tile number and tile length values in the j2k_read_sot function. Until patched, avoid processing untrusted JPEG 2000 files with OpenJPEG.

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:= 1.5

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Identify OpenJPEG installation and version
    Run 'openvolw --version' or check library file version (e.g., 'pkg-config --modversion openjpeg' or 'ldd <binary> | grep openjpeg')
    Affected if The installed version is exactly 1.5
  2. Locate the vulnerable j2k.c file
    Find OpenJPEG source or binary files (typically in /usr/include/openjpeg-1.5/ or similar) and verify j2k.c exists with the j2k_read_sot function
    Affected if j2k.c with j2k_read_sot function is present in version 1.5
  3. Determine if JPEG 2000 processing is enabled
    Check application configuration or code for JPEG 2000 support (look for .jp2, .j2k, .j2c file handling or OpenJPEG library linking)
    Affected if The environment processes JPEG 2000 image files using OpenJPEG 1.5
  4. Check for untrusted JPEG 2000 file input
    Review logs, file upload mechanisms, or image processing pipelines that accept JPEG 2000 files from external sources
    Affected if Untrusted or user-supplied JPEG 2000 files are being processed by the OpenJPEG 1.5 library

You are affected if OpenJPEG version 1.5 is installed and processes JPEG 2000 files (including potentially untrusted ones) using the j2k_read_sot function in j2k.c.

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 a patched version that includes proper bounds checking on tile number and tile length values in the j2k_read_sot function. Until patched, avoid processing untrusted JPEG 2000 files with OpenJPEG.

Recommended fix Moderate confidence

OpenJPEG 1.5.1 or later (preferably OpenJPEG 2.x stable release)

  1. 1. Identify all systems and applications that use OpenJPEG 1.5 library
  2. 2. Download the fixed OpenJPEG version (1.5.1 or later) from the official OpenJPEG repository or your Linux distribution's package manager
  3. 3. Replace the vulnerable libopenjpeg library files with the fixed version
  4. 4. Rebuild or restart any applications dynamically linked to OpenJPEG to ensure they load the patched library
  5. 5. Verify the patch was applied by checking the OpenJPEG version (e.g., using `opj_version` command or checking library version)
  6. 6. Test that JPEG 2000 image processing still functions correctly with the updated library
Caveat Minor: Verify compatibility with any applications relying on specific OpenJPEG 1.5 behaviors; OpenJPEG 2.x has API changes that may require code adjustments

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

Fix this in Openjpeg Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-3358 — 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-2012-3358 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