CVE-2015-8665
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 · uneditedtif_getimage.c in LibTIFF 4.0.6 allows remote attackers to cause a denial of service (out-of-bounds read) via the SamplesPerPixel tag in a TIFF image.
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 confidenceAn out-of-bounds read vulnerability exists in tif_getimage.c of LibTIFF 4.0.6, where a maliciously crafted TIFF image with a crafted SamplesPerPixel tag can cause the library to read beyond allocated buffer boundaries, leading to denial of service.
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= 4.0.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed LibTIFF versionRun 'tiffinfo -version' or check your package manager for the installed libtiff version (e.g., dpkg -l libtiff, rpm -qa libtiff, or check /usr/include/tiffio.h for TIFF_VERSION definition)Affected if The installed version is exactly 4.0.6
-
Locate the vulnerable tif_getimage.c componentCheck if the LibTIFF library file exists on the system (typically /usr/lib/libtiff.so or /usr/lib64/libtiff.so on Linux, or search for tif_getimage.c in source installations)Affected if LibTIFF 4.0.6 library files are present on the system
-
Determine if TIFF image processing is in useSearch for processes or applications that handle TIFF files (look for usage of libtiff in running processes via 'ldd' on binaries, or check application logs for TIFF file processing)Affected if Applications or services process incoming or user-provided TIFF images using the vulnerable LibTIFF version
-
Inspect for malicious TIFF samples in input pathsIf TIFF processing exists, examine directories where untrusted TIFF files may be uploaded or received; use 'file *.tiff' or 'tiffinfo' to inspect SamplesPerPixel values in any found imagesAffected if Untrusted TIFF files with anomalous SamplesPerPixel tags can be processed by the vulnerable library
You are affected if LibTIFF version 4.0.6 is installed AND your environment processes untrusted TIFF images using this library, allowing a crafted SamplesPerPixel tag to trigger the out-of-bounds read in tif_getimage.c.
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 dataUpdate LibTIFF to version 4.0.7 or later, which contains the patch for this vulnerability. If immediate patching is not feasible, implement input validation on TIFF files before processing to reject files with malformed SamplesPerPixel values.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8665 — 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-2015-8665 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