CVE-2010-2443
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 · uneditedThe OJPEGReadBufferFill function in tif_ojpeg.c in LibTIFF before 3.9.3 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via an OJPEG image with undefined strip offsets, related to the TIFFVGetField function.
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 NULL pointer dereference vulnerability exists in LibTIFF's OJPEGReadBufferFill function in tif_ojpeg.c. When processing a specially crafted OJPEG image with undefined strip offsets, the function attempts to dereference a NULL pointer (related to TIFFVGetField), causing the application to crash.
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<= 3.9.2= 3.4= 3.5.1= 3.5.2= 3.5.3= 3.5.4= 3.5.5= 3.5.6= 3.5.7= 3.6.0= 3.6.1= 3.7.0CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Identify installed LibTIFF versionRun 'tiffinfo -version' or check the libtiff library file (e.g., libtiff.so) for version metadata. On Debian/Ubuntu: dpkg -l libtiff*. On RedHat/CentOS: rpm -qa | grep tiff.Affected if The installed version matches <= 3.9.2 or any of these specific versions: 3.4, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.5.5, 3.5.6, 3.5.7, 3.6.0, 3.6.1, 3.7.0
-
Determine if OJPEG image processing is in useInspect any TIFF image files processed by the system using 'tiffinfo <file>' and look for 'Compression: OJPEG' or 'Compression: 6' in the output. Check application logs or code that processes TIFF files to see if OJPEG compression is being decoded.Affected if The system processes OJPEG-compressed TIFF images (compression type 6) using the affected LibTIFF library
-
Verify if images have undefined strip offsetsRun 'tiffinfo -j' on suspect OJPEG images to inspect tag 273 (StripOffsets). Alternatively, use 'tiffdump' and check if StripOffsets is missing, zero, or undefined for OJPEG images.Affected if OJPEG images being processed have undefined, missing, or zero-valued strip offset fields (tag 273)
A system is affected if it runs a vulnerable LibTIFF version (3.4 through 3.9.2) and processes OJPEG-compressed TIFF images that contain undefined strip offsets, which triggers the NULL pointer dereference in OJPEGReadBufferFill.
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 dataUpgrade LibTIFF to version 3.9.3 or later, or implement input validation to reject OJPEG images with undefined strip offsets before processing.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2443 — 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-2443 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