Ubuntu LinuxOperating system · Canonical
CVE-2010-2067
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 · uneditedStack-based buffer overflow in the TIFFFetchSubjectDistance function in tif_dirread.c in LibTIFF before 3.9.4 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a long EXIF SubjectDistance field in a TIFF file.
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 confidenceStack-based buffer overflow in LibTIFF's TIFFFetchSubjectDistance function in tif_dirread.c when parsing long EXIF SubjectDistance fields in TIFF files. This allows remote attackers to cause denial of service via application crash or potentially execute arbitrary code by supplying a crafted TIFF file.
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
Ubuntu LinuxOperating system
= 6.06= 8.04= 9.04= 9.10= 10.04< 3.9.4CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Check if LibTIFF library is installedOn Debian/Ubuntu: dpkg -l | grep libtiff. On Red Hat/CentOS: rpm -qa | grep libtiff. Alternatively, check for the presence of libtiff shared library files in /usr/lib or /usr/lib64.Affected if LibTIFF library files are present on the system
-
Determine the installed LibTIFF versionOn Debian/Ubuntu: dpkg -l libtiff* or apt-cache policy libtiff*. On Red Hat/CentOS: rpm -q libtiff. You can also use: ldd /path/to/application 2>/dev/null | grep tiff or check the library directly with: strings /usr/lib/libtiff.so* | grep "^3\." | head -1Affected if The version number returned is less than 3.9.4 or cannot be determined to be 3.9.4 or higher
-
Identify applications or services using LibTIFFSearch for binaries that link against libtiff: ldd $(which * 2>/dev/null) 2>/dev/null | grep -i tiff. Check for image processing tools like tiffinfo, tiff2pdf, convert (ImageMagick), or custom applications that process TIFF files.Affected if Any application that processes TIFF files using LibTIFF is present and the library version is below 3.9.4
-
Verify Ubuntu kernel/package version if using system packagesFor Ubuntu systems, check: cat /etc/lsb-release to confirm the version matches affected releases (6.06, 8.04, 9.04, 9.10, 10.04). Then check the installed libtiff package version with: dpkg -l | grep -i tiffAffected if Running Ubuntu 6.06, 8.04, 9.04, 9.10, or 10.04 with LibTIFF package version below what is provided in the fixed release
A system is affected if it has LibTIFF installed with a version lower than 3.9.4 and uses any functionality to parse TIFF files containing EXIF SubjectDistance metadata.
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 data3.9.4
Upgrade LibTIFF to version 3.9.4 or later. Avoid processing untrusted TIFF files until the library is updated.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2067 — 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-2010-2067 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