dbcve.org
Debian LinuxOperating system · Debian

CVE-2017-17480

CRITICAL · 9.8 CVSS v3.1 Published 2017-12-08
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
In OpenJPEG 2.3.0, a stack-based buffer overflow was discovered in the pgxtovolume function in jp3d/convert.c. The vulnerability causes an out-of-bounds write, which may lead to remote denial of service or possibly remote code execution.

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

OpenJPEG 2.3.0 contains a stack-based buffer overflow vulnerability in the pgxtovolume function within jp3d/convert.c. The vulnerability allows an out-of-bounds write operation, which can be triggered during JP3D (JPEG 2000 3D) image processing, potentially leading to denial of service or remote code execution.

MitigationUpgrade to a patched version of OpenJPEG beyond 2.3.0 that addresses this vulnerability. If immediate patching is not possible, disable or restrict processing of untrusted JP3D files.

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
Debian LinuxOperating system
Affected:= 8.0= 9.0
Ubuntu LinuxOperating system
Affected:= 18.04
OpenjpegApplication
Affected:= 2.3.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify OpenJPEG version
    Run 'opj_version' command, or check package manager output: 'dpkg -l | grep openjpeg' (Debian/Ubuntu), or examine shared library version via 'ldconfig -p | grep openjpeg'
    Affected if Version is exactly 2.3.0
  2. Confirm JP3D support is compiled in
    Check if the jp3d module exists in the OpenJPEG installation directory, or run 'opj_decompress -h' and look for JP3D-related options, or examine the binary with 'objdump -T <binary> | grep -i jp3d'
    Affected if JP3D decoding capability is present in the installed binary
  3. Locate vulnerable source file
    Verify the presence of convert.c in the jp3d subdirectory of the OpenJPEG source tree or installation: 'find /usr -name convert.c -path "*/jp3d/*" 2>/dev/null'
    Affected if The file jp3d/convert.c exists in the installed version and contains the pgxtovolume function
  4. Check for JP3D file processing activity
    Review application logs or file system for recent processing of .jp3d or .j3d files, or inspect any JP3D-enabled image conversion workflows
    Affected if JP3D image files have been processed by the OpenJPEG library

The environment is affected if OpenJPEG version 2.3.0 is installed and JP3D image processing capability is available and has been used.

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

Upgrade to a patched version of OpenJPEG beyond 2.3.0 that addresses this vulnerability. If immediate patching is not possible, disable or restrict processing of untrusted JP3D files.

Recommended fix High confidence

OpenJPEG 2.3.1 or later (fixed release)

  1. Update your system's package list: sudo apt-get update (for Debian/Ubuntu)
  2. Upgrade OpenJPEG to the latest available version: sudo apt-get upgrade libopenjp2-7 or sudo apt-get upgrade openjpeg
  3. Alternatively, install the fixed version directly: sudo apt-get install libopenjp2-7=2.3.1+dfsg-1+deb10u1 or later (Debian 10)
  4. Verify the installed version matches a version higher than 2.3.0: dpkg -l | grep openjpeg
  5. If using OpenJPEG as a dependency, rebuild or reinstall dependent packages to ensure they use the fixed version
Caveat Upgrading OpenJPEG libraries may require rebuilding dependent applications; test thoroughly in non-production environment first

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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