Skip to content
Noroxi
CVE-2009-2285· NVD / CVE Program· CNA mitre

Buffer underflow in the LZWDecodeCompat function in libtiff 3.8.2 allows context-dependent attackers to cause a denial of service (crash) vi

Buffer underflow in the LZWDecodeCompat function in libtiff 3.8.2 allows context-dependent attackers to cause a denial of service (crash) via a crafted TIFF image, a different vulnerability than CVE-2008-2327.

MediumCVSS 4.3 · v2.0—Proof of concept Fix available
Published
Jul 1, 2009
Updated
Jun 16, 2026
EPSS
9.0% · 95th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 9.0%

Affected systems

VendorProduct
libtifflibtiff

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • libtiff libtiff3.8.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12tiffbefore 3.8.2-123.8.2-12
Debian:4.0tiffbefore 3.8.2-7+etch33.8.2-7+etch3
Debian:5.0tiffbefore 3.8.2-11.23.8.2-11.2
openSUSE:Tumbleweedtiffbefore 4.0.7-1.14.0.7-1.1
Red Hat:enterprise_linux:3::aslibtiffbefore 0:3.5.7-33.el30:3.5.7-33.el3
Red Hat:enterprise_linux:3::aslibtiff-debuginfobefore 0:3.5.7-33.el30:3.5.7-33.el3
Red Hat:enterprise_linux:3::aslibtiff-develbefore 0:3.5.7-33.el30:3.5.7-33.el3
Red Hat:enterprise_linux:4::aslibtiffbefore 0:3.6.1-12.el4_8.40:3.6.1-12.el4_8.4
Red Hat:enterprise_linux:4::aslibtiff-debuginfobefore 0:3.6.1-12.el4_8.40:3.6.1-12.el4_8.4
Red Hat:enterprise_linux:4::aslibtiff-develbefore 0:3.6.1-12.el4_8.40:3.6.1-12.el4_8.4
Red Hat:enterprise_linux:5::client_workstationlibtiffbefore 0:3.8.2-7.el5_3.40:3.8.2-7.el5_3.4
Red Hat:enterprise_linux:5::client_workstationlibtiff-debuginfobefore 0:3.8.2-7.el5_3.40:3.8.2-7.el5_3.4
Red Hat:enterprise_linux:5::client_workstationlibtiff-develbefore 0:3.8.2-7.el5_3.40:3.8.2-7.el5_3.4

Other highest-scoring records for the same primary product.

  • CVE-2006-3459Multiple stack-based buffer overflows in the TIFF library (libtiff) before 3.8.2, as used in Adobe Reader 9.3.0 and other products, allow co
    46Plan
  • CVE-2004-1308Integer overflow in (1) tif_dirread.c and (2) tif_fax3.c for libtiff 3.5.7 and 3.7.0 allows remote attackers to execute arbitrary code via a
    44Plan
  • CVE-2018-12900Heap-based buffer overflow in the cpSeparateBufToContigBuf function in tiffcp.c in LibTIFF 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0beta7, 4.
    43Plan
  • CVE-2015-8668Heap-based buffer overflow in the PackBitsPreEncode function in tif_packbits.c in bmp2tiff in libtiff 4.0.6 and earlier allows remote attack
    43Plan
  • CVE-2004-0929Heap-based buffer overflow in the OJPEGVSetField function in tif_ojpeg.c for libtiff 3.6.1 and earlier, when compiled with the OJPEG_SUPPORT
    42Plan
  • CVE-2016-9540tools/tiffcp.c in libtiff 4.0.6 has an out-of-bounds write on tiled images with odd tile width versus image width.
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:tiff3.8.2-12 · Debian:12Package registry (OSV)
opensuse:tiff4.0.7-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:libtiff0:3.5.7-33.el3 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
red hat:libtiff-debuginfo0:3.5.7-33.el3 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
red hat:libtiff-devel0:3.5.7-33.el3 · Red Hat:enterprise_linux:3::asPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrydos2009-05-21
Exploit-DB entrydos2009-11-12

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-41 d
  2. Published
  3. TodaySep 30, 2026+6300 d
EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    none
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    None
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:N/C:P/I:N/A:N

    nvd-primary

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records