CVE-2025-8851
BaseFortify
Publication date: 2025-08-11
Last updated on: 2025-10-30
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| libtiff | libtiff | to 4.5.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-121 | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8851 is a stack-based buffer overflow vulnerability in LibTIFF versions up to 4.5.1, specifically in the tiffcrop tool's function readSeparateStripsetoBuffer. It occurs because the tool improperly handles negative return values from TIFF strip reading operations and fails to validate margin calculations, leading to out-of-bounds memory access on the stack. This can cause memory corruption, application crashes, or denial of service when processing crafted TIFF files. Exploitation requires local access. [2, 3]
How can this vulnerability impact me? :
This vulnerability can compromise the confidentiality, integrity, and availability of the affected system by causing memory corruption and application crashes (denial of service). Since it is a stack-based buffer overflow, it may allow an attacker with local access to execute arbitrary code or disrupt normal operation of the LibTIFF tiffcrop utility, potentially affecting systems that process malicious TIFF files. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability is a local stack-based buffer overflow in the tiffcrop tool of LibTIFF and requires local access to exploit. Detection involves checking the version of LibTIFF installed (versions up to 4.5.1 are affected) and monitoring for crashes or abnormal behavior when processing TIFF files with tiffcrop. Since the vulnerability is triggered by crafted TIFF files causing memory corruption, running tiffcrop with AddressSanitizer or similar memory error detection tools on suspicious TIFF files can help detect the issue. Specific commands include: 1) Checking LibTIFF version: `tiffcrop -v` or `tiffcrop --version` 2) Running tiffcrop under AddressSanitizer or a debugger with crafted TIFF inputs to detect buffer overflows. 3) Monitoring system logs for crashes or denial of service related to tiffcrop. No public exploit or network-based detection commands are available since exploitation requires local access. [3]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to apply the patch identified by commit 8a7a48d7a645992ca83062b3a1873c951661e2b3 to update LibTIFF to a fixed version beyond 4.5.1. Users should update their LibTIFF installation, especially the tiffcrop utility, to the patched version to prevent exploitation. Additionally, restrict local access to trusted users only, as exploitation requires local access. Avoid processing untrusted or crafted TIFF files with vulnerable versions until patched. [1, 2]