dbcve.org
Exiv2Application

CVE-2017-1000127

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 heap buffer overflow in tiff 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 heap buffer overflow vulnerability in its TIFF image metadata parser. The vulnerability allows memory corruption when processing specially crafted TIFF files, potentially enabling denial of service or potentially arbitrary code execution depending on exploitation context.

MitigationUpgrade Exiv2 to a patched version beyond 0.26. If upgrading is not immediately feasible, restrict processing of untrusted TIFF files and implement input validation as a temporary mitigation.

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. Confirm Exiv2 is installed
    Run command: which exiv2 or dpkg -l | grep exiv2 (Debian/Ubuntu) or rpm -qa | grep exiv2 (RHEL/CentOS)
    Affected if Exiv2 is not installed means not affected
  2. Determine installed Exiv2 version
    Run command: exiv2 --version and compare output to the affected version 0.26
    Affected if Installed version is exactly 0.26
  3. Check if TIFF support is compiled in
    Run command: exiv2 --version and look for 'tiff' in the supported formats list, or check if libexiv2 was built with TIFF support via package manager
    Affected if TIFF support is present and the installed version is 0.26
  4. Identify TIFF file processing in your environment
    Search for workflows, scripts, or applications that process TIFF files using Exiv2: grep -r 'exiv2.*tiff' or review application logs/configs that invoke exiv2 on .tiff/.tif files
    Affected if Your systems process TIFF files using Exiv2 and the version is 0.26

You are affected if Exiv2 version 0.26 is installed and your environment processes TIFF image files with it.

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

Upgrade Exiv2 to a patched version beyond 0.26. If upgrading is not immediately feasible, restrict processing of untrusted TIFF files and implement input validation as a temporary mitigation.

Fix this in Exiv2 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-2017-1000127 — 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-1000127 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