CVE-2022-0908

7.7 HIGH

📋 TL;DR

This vulnerability in libtiff allows an attacker to cause denial of service by passing a null pointer to memcpy() when processing specially crafted TIFF files. The flaw occurs in the TIFFFetchNormalTag() function and affects applications that use libtiff to parse TIFF images. Systems using libtiff versions up to 4.3.0 are vulnerable.

💻 Affected Systems

Products:
  • libtiff
Versions: All versions up to and including 4.3.0
Operating Systems: Linux, Windows, macOS, BSD - any OS using vulnerable libtiff
Default Config Vulnerable: ⚠️ Yes
Notes: Any application linking against vulnerable libtiff versions is affected when processing TIFF files.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete application crash leading to denial of service, potentially affecting availability of services that process TIFF files.

🟠

Likely Case

Application crash when processing malicious TIFF files, causing temporary service disruption.

🟢

If Mitigated

No impact if patched or if TIFF file processing is restricted to trusted sources.

🌐 Internet-Facing: MEDIUM - Applications accepting TIFF uploads from untrusted sources are vulnerable to DoS attacks.
🏢 Internal Only: LOW - Internal systems typically process trusted TIFF files, reducing exposure.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires only a crafted TIFF file; no authentication needed. Public proof-of-concept exists in the GitLab issue.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: libtiff 4.4.0 and later

Vendor Advisory: https://gitlab.com/libtiff/libtiff/-/commit/a95b799f65064e4ba2e2dfc206808f86faf93e85

Restart Required: Yes

Instructions:

1. Update libtiff to version 4.4.0 or later. 2. For Linux: Use package manager (apt-get update && apt-get upgrade libtiff5, yum update libtiff, etc.). 3. For Windows: Download updated version from libtiff website. 4. Recompile applications if using static linking. 5. Restart affected services.

🔧 Temporary Workarounds

Restrict TIFF file processing

all

Block or validate TIFF files from untrusted sources before processing.

Use file type validation

all

Implement strict file type validation to reject malformed TIFF files.

🧯 If You Can't Patch

  • Implement network filtering to block TIFF files from untrusted sources.
  • Deploy application-level controls to validate TIFF files before processing.

🔍 How to Verify

Check if Vulnerable:

Check libtiff version: tiffinfo --version or check package version via package manager.

Check Version:

tiffinfo --version 2>&1 | head -1

Verify Fix Applied:

Confirm libtiff version is 4.4.0 or later and test with known malicious TIFF file.

📡 Detection & Monitoring

Log Indicators:

  • Application crashes with segmentation faults when processing TIFF files
  • Error logs containing memcpy or TIFFFetchNormalTag failures

Network Indicators:

  • Unusual TIFF file uploads to web applications
  • TIFF files with abnormal structure

SIEM Query:

source="application.log" AND ("segmentation fault" OR "memcpy" OR "TIFFFetchNormalTag")

🔗 References

📤 Share & Export