dbcve.org
Exiv2Application

CVE-2017-1000128

MEDIUM · 5.5 CVSS v3.0 Published 2017-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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
Exiv2 0.26 contains a stack out of bounds read in JPEG2000 parser

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

Exiv2 0.26 contains a stack out-of-bounds read vulnerability in its JPEG2000 image parser. The parser reads beyond the boundaries of a stack-allocated buffer when processing malicious or crafted JPEG2000 images, potentially allowing disclosure of stack memory contents.

MitigationUpdate Exiv2 to a patched version that addresses this vulnerability. If updating is not immediately feasible, avoid processing untrusted JPEG2000 images with vulnerable versions of Exiv2.

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
Exiv2Application
Affected:= 0.26

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/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 installed Exiv2 version
    Run 'exiv2 --version' or 'exiv2 -V' to display the installed version number
    Affected if Version displayed is 0.26 exactly
  2. Verify Exiv2 binary path
    Run 'which exiv2' or 'where exiv2' to confirm the executable location and ensure it matches the affected package
    Affected if The binary located is version 0.26
  3. Confirm JPEG2000 support is enabled
    Run 'exiv2 -V' and look for 'jp2' or 'jpeg2000' in the supported formats or codecs list
    Affected if JPEG2000 support is listed as available (vulnerability only applies when JP2 parsing is enabled)
  4. Identify JPEG2000 image files in the environment
    Search for .jp2, .j2k, .jpf, or .jpx file extensions using 'find . -name "*.jp2"' or similar directory searches
    Affected if JPEG2000 images exist that could be processed by the vulnerable Exiv2 version

You are affected if Exiv2 version 0.26 is installed AND JPEG2000 support is enabled, meaning processing a crafted JPEG2000 image could trigger the stack out-of-bounds read.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Exiv2 to a patched version that addresses this vulnerability. If updating is not immediately feasible, avoid processing untrusted JPEG2000 images with vulnerable versions of Exiv2.

Fix this in Exiv2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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