CVE-2017-11336
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 · uneditedThere is a heap-based buffer over-read in the Image::printIFDStructure function in image.cpp in Exiv2 0.26. A Crafted input will lead to a remote denial of service attack.
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 confidenceA heap-based buffer over-read vulnerability exists in the Image::printIFDStructure function in image.cpp of Exiv2 0.26. When parsing specially crafted image files, the function reads beyond allocated buffer boundaries, causing a denial of service condition. This is a bounds-checking issue in IFD (Image File Directory) structure parsing.
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= 0.26CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Exiv2 versionRun 'exiv2 --version' or check the installed package version using your system's package manager (e.g., 'dpkg -l | grep exiv2', 'rpm -qi exiv2', or 'brew list exiv2').Affected if The version listed is exactly 0.26
-
Confirm Exiv2 binary or library presenceLocate the Exiv2 binary or shared library on the system using 'which exiv2' or 'find /usr -name "*exiv2*" -type f'Affected if Exiv2 version 0.26 binary or library exists on the system
-
Check for IFD parsing usageReview application logs or code that invokes Exiv2 to parse image metadata, particularly TIFF, JPEG, or other formats containing EXIF data. Exiv2 parses IFD structures when extracting metadata from images.Affected if Exiv2 0.26 is used to parse metadata from image files, which triggers the Image::printIFDStructure function in image.cpp
-
Identify untrusted image processingDetermine whether Exiv2 0.26 processes image files from untrusted or external sources, such as user uploads, downloaded images, or attachments.Affected if Exiv2 0.26 processes image files from untrusted or crafted sources, enabling the buffer over-read condition to trigger
You are affected if Exiv2 version 0.26 is installed and used to parse metadata from image files, particularly untrusted or crafted ones, because the vulnerability lies in the IFD structure parsing code within this specific version.
Generated from the published advisory. Verify against your own configuration.
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 dataAvoid processing untrusted or crafted image files with Exiv2 0.26. Upgrade to a patched version of Exiv2 that addresses this vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-11336 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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