dbcve.org
LibtiffApplication

CVE-2022-34266

MEDIUM · 5.5 CVSS v3.1 Published 2022-07-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
The libtiff-4.0.3-35.amzn2.0.1 package for LibTIFF on Amazon Linux 2 allows attackers to cause a denial of service (application crash), a different vulnerability than CVE-2022-0562. When processing a malicious TIFF file, an invalid range may be passed as an argument to the memset() function within TIFFFetchStripThing() in tif_dirread.c. This will cause TIFFFetchStripThing() to segfault after use of an uninitialized resource.

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 confidence

A denial-of-service vulnerability exists in libtiff's TIFFFetchStripThing() function in tif_dirread.c. When processing a maliciously crafted TIFF file, an invalid range is passed to memset(), causing the function to use an uninitialized resource and trigger a segfault. This affects libtiff-4.0.3-35.amzn2.0.1 on Amazon Linux 2.

MitigationUpdate libtiff to the latest patched version provided by Amazon Linux 2 security advisories. Until patched, avoid processing untrusted or unknown TIFF files with applications using this library.

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
LibtiffApplication
Affected:= 4.0.3-35

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed libtiff version
    Run 'rpm -q libtiff' on Amazon Linux 2 systems to retrieve the installed package version
    Affected if The version shown is 4.0.3-35 (exactly matching the affected version)
  2. Verify libtiff library file presence
    Run 'ldconfig -p | grep -i tiff' to list linked TIFF libraries, or check /usr/lib64/libtiff* for library files
    Affected if libtiff.so libraries exist on the system indicating the library is installed
  3. Identify applications using libtiff
    Run 'ldd /usr/bin/* 2>/dev/null | grep -l libtiff' or check common image tools: 'which convert' (ImageMagick), 'which gimp', 'which tiffinfo', then 'ldd' on those binaries to confirm libtiff dependency
    Affected if Any image processing applications (convert, gimp, tiffinfo, etc.) are linked against libtiff
  4. Check for untrusted TIFF file processing scenarios
    Review application logs, cron jobs, or services that process TIFF files from external or untrusted sources, such as file uploads, email attachments, or network-based file transfers
    Affected if Applications process TIFF files from users, email, web uploads, or other untrusted sources

A system is affected if it runs libtiff version 4.0.3-35 AND has applications that process TIFF files, especially from untrusted sources, as exploitation requires processing a maliciously crafted TIFF file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update libtiff to the latest patched version provided by Amazon Linux 2 security advisories. Until patched, avoid processing untrusted or unknown TIFF files with applications using this library.

Recommended fix Moderate confidence

libtiff 4.4.0 or later stable release

  1. 1. Identify all systems running the affected libtiff version (4.0.3-35) using your system's package manager (e.g., rpm -qa | grep tiff or dpkg -l | grep tiff)
  2. 2. Back up any critical data and ensure you have a recovery plan
  3. 3. Update the package via your distribution's package manager: For Amazon Linux 2, run: sudo yum update libtiff
  4. 4. Alternatively, download and compile the latest stable libtiff release from the official source (https://gitlab.com/libtiff/libtiff)
  5. 5. After updating, restart any applications that use libtiff to ensure they load the patched library
  6. 6. Verify the fix by checking the new libtiff version (tiffinfo -version) and re-testing with the previously vulnerable TIFF file
Caveat Major version upgrades (e.g., 4.0.x to 4.4.x) may introduce API/ABI changes; test applications that depend on libtiff in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Libtiff Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34266 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34266 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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