Memory Leak Vulnerability in TIFF Package: CVE-2017-9936

tiff Updated 02 Oct 2025

Summary

26/06/2017
N/A
Yes i
Medium
6.5

ALPINE-CVE-2017-9936: In LibTIFF 4.0.8, there is a memory leak in tif_jbig.c. A crafted TIFF document can lead to a memory leak resulting in a remote denial of service attack. Affects tiff versions < 4.0.8-r1. Fixed in 4.0.8-r1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The TIFF (Tagged Image File Format) package is widely used for handling raster graphics images, particularly in the context of digital photography and scanning. It supports multiple layers and channels, making it a versatile choice for image storage. However, the package has been found to have a vulnerability that can lead to memory leaks, which can be exploited in certain scenarios.

Vulnerability Detail

In LibTIFF version 4.0.8, a memory leak exists in the tif_jbig.c file. This vulnerability can be triggered by a specially crafted TIFF document, leading to a remote denial of service attack. The memory leak occurs when the application fails to release allocated memory, potentially exhausting system resources and causing the application to crash or become unresponsive. The CVSS score for this vulnerability is 6.5, indicating a moderate severity level.

How To Fix

Minimum fixed version

4.0.8-r1

This is the first release that contains the fix.

sudo apk add --upgrade tiff

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, avoid opening untrusted TIFF files or limit the use of the TIFF package until the update is applied. Additionally, consider using alternative image formats that do not exhibit this vulnerability.

Conclusion

The memory leak vulnerability in the TIFF package (CVE-2017-9936) poses a risk of denial of service through crafted TIFF documents. It is crucial to update to the patched version to ensure system stability and security. Users should also consider using Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for tiff →

Share this vulnerability

FAQ

CVE-2017-9936 is a vulnerability in the TIFF package that can lead to a memory leak, potentially causing a denial of service.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Exploiting this vulnerability can lead to a denial of service, where the application may crash or become unresponsive due to exhausted memory resources.

Yes, the patch is available in version 4.0.8-r1 of the TIFF package. Updating to this version will resolve the issue.

If an immediate update is not possible, refrain from using the TIFF package with untrusted files and consider alternative image formats.

Related vulnerabilities

Recent vulnerabilities recorded for tiff.

How To Fix

Minimum fixed version

4.0.8-r1

This is the first release that contains the fix.

sudo apk add --upgrade tiff

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback