CVE-2025-9900
Libtiff: libtiff write-what-where
Description
A flaw was found in Libtiff. This vulnerability is a "write-what-where" condition, triggered when the library processes a specially crafted TIFF image file. By providing an abnormally large image height value in the file's metadata, an attacker can trick the library into writing attacker-controlled color data to an arbitrary memory location. This memory corruption can be exploited to cause a denial of service (application crash) or to achieve arbitrary code execution with the permissions of the user.
INFO
Published Date :
Sept. 23, 2025, 5:15 p.m.
Last Modified :
Oct. 13, 2025, 2:15 a.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 53f830b8-0a3f-465b-8143-3b8a9948e749 | ||||
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Apply the latest security patches for Libtiff.
- Update the Libtiff library to a secure version.
- Sanitize image height input values.
- Validate TIFF file metadata rigorously.
Public PoC/Exploit Available at Github
CVE-2025-9900 has a 2 public
PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-9900.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-9900 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-9900
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
This is a placeholder for a vulnerability discovered in LibTiff
DSA and DLA for Debian last 14 days
Python
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-9900 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-9900 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
Oct. 13, 2025
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHSA-2025:17738 Added Reference https://access.redhat.com/errata/RHSA-2025:17739 Added Reference https://access.redhat.com/errata/RHSA-2025:17740 -
CVE Modified by [email protected]
Oct. 09, 2025
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHSA-2025:17710 -
CVE Modified by [email protected]
Oct. 09, 2025
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHSA-2025:17651 Added Reference https://access.redhat.com/errata/RHSA-2025:17675 -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Sep. 23, 2025
Action Type Old Value New Value Added Reference https://github.com/SexyShoelessGodofWar/LibTiff-4.7.0-Write-What-Where?tab=readme-ov-file -
New CVE Received by [email protected]
Sep. 23, 2025
Action Type Old Value New Value Added Description A flaw was found in Libtiff. This vulnerability is a "write-what-where" condition, triggered when the library processes a specially crafted TIFF image file. By providing an abnormally large image height value in the file's metadata, an attacker can trick the library into writing attacker-controlled color data to an arbitrary memory location. This memory corruption can be exploited to cause a denial of service (application crash) or to achieve arbitrary code execution with the permissions of the user. Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Added CWE CWE-123 Added Reference https://access.redhat.com/security/cve/CVE-2025-9900 Added Reference https://bugzilla.redhat.com/show_bug.cgi?id=2392784 Added Reference https://github.com/SexyShoelessGodofWar/LibTiff-4.7.0-Write-What-Where?tab=readme-ov-file