dbcve.org
OpenjpegApplication · Uclouvain

CVE-2013-4289

HIGH · 10.0 CVSS v2.0 Published 2014-04-18
Fix available
A fix is available. Upgrade to after 1.5.1 or later.
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 integer overflows in lib/openjp3d/jp3d.c in OpenJPEG before 1.5.2 allow remote attackers to have unspecified impact and vectors, which trigger a heap-based buffer overflow.

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

Multiple integer overflows in the JP3D (JPEG 2000 Part 3) library component (lib/openjp3d/jp3d.c) in OpenJPEG before version 1.5.2 allow remote attackers to trigger heap-based buffer overflows through unspecified vectors, potentially leading to arbitrary code execution.

MitigationUpgrade OpenJPEG to version 1.5.2 or later to patch the integer overflows. Identify and update all applications or systems that bundle or link against the vulnerable OpenJPEG library.

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.1= 1.3= 1.4= 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 library version
    Locate the OpenJPEG library on the system (commonly as libopenjp3d.so, openjp3d.dll, or part of a bundled library) and query its version using the system's package manager, library version inspection tools, or by checking version information embedded in the library file itself
    Affected if The version is 1.3, 1.4, 1.5, or any version up to and including 1.5.1 (versions prior to 1.5.2 are affected)
  2. Confirm the JP3D component is present
    Verify that the jp3d.c derived library component (libopenjp3d or equivalent) exists in the OpenJPEG installation directory - the vulnerability exists specifically in the JP3D (JPEG 2000 Part 3) library component at lib/openjp3d/jp3d.c
    Affected if The jp3d library component is present and linked into the OpenJPEG build, indicating the vulnerable code path exists in the environment
  3. Determine if JP3D functionality is actively used
    Inspect application logs, configuration files, or runtime behavior to check whether any application is processing JP3D/JPEG 2000 Part 3 format files or calling jp3d-related functions - the integer overflows are triggered through unspecified vectors when the JP3D component processes specific input
    Affected if Any application on the system processes JP3D-format images or invokes the jp3d library functions, enabling the attack vector
  4. Identify applications linking to vulnerable OpenJPEG
    Scan the system for binaries or applications that link against the OpenJPEG library (check dependencies using tools like ldd, objdump, or similar) - many applications may bundle or link to the library without the user being aware
    Affected if Applications dynamically or statically link to a vulnerable OpenJPEG version (1.3, 1.4, 1.5, or <=1.5.1)

The environment is affected if OpenJPEG version 1.3, 1.4, 1.5, or any version through 1.5.1 is installed and any application actively uses the JP3D library component or links to the vulnerable library.

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
Upgrade available Upgrade to a release after 1.5.1
Interim mitigation

Upgrade OpenJPEG to version 1.5.2 or later to patch the integer overflows. Identify and update all applications or systems that bundle or link against the vulnerable OpenJPEG library.

Recommended fix High confidence

OpenJPEG 1.5.2

  1. Identify the current OpenJPEG version installed in your system
  2. Download OpenJPEG version 1.5.2 or later from the official OpenJPEG repository or distribution package manager
  3. Backup any existing OpenJPEG installations and dependent applications
  4. Install the upgraded version (1.5.2 or later) using standard build/installation procedures for your platform
  5. Verify the new version is correctly installed by checking the library version
  6. Test that applications using OpenJPEG function correctly with the new version

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 the upgrade done

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-2013-4289 — 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-2013-4289 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