CVE-2025-8176
BaseFortify
Publication date: 2025-07-26
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| libtiff | libtiff | to 4.7.0 (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-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8176 is a critical use-after-free vulnerability in LibTIFF versions up to 4.7.0, specifically in the tiffmedian tool's get_histogram function (tools/tiffmedian.c). It occurs when processing malformed TIFF files, causing the program to access memory after it has been freed. This improper memory management can lead to crashes, unexpected behavior, or arbitrary code execution. The vulnerability requires local access to exploit and has a publicly available proof-of-concept. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by causing program crashes, unexpected behavior, or allowing an attacker to execute arbitrary code on your system. Since it affects the confidentiality, integrity, and availability of the affected system, it can lead to system compromise or denial of service. Exploitation requires local access but is considered easy due to the availability of a public proof-of-concept exploit. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by running the vulnerable tiffmedian tool from LibTIFF version 4.7.0 with a crafted proof-of-concept (PoC) malformed TIFF file designed to trigger the use-after-free condition. A suggested command to reproduce and detect the issue is: ``` ./tools/tiffmedian -C 256 -c lzw:2 -f poc /tmp/output.tif ``` where "poc" is the crafted TIFF file that triggers the vulnerability. During execution, using AddressSanitizer (ASan) can help detect heap-use-after-free errors, as ASan will output warnings and stack traces indicating the memory misuse. This approach requires local access and the ability to build or run the vulnerable binary with ASan enabled. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to apply the official patch identified by commit fe10872e53efba9cc36c66ac4ab3b41a839d5172 to the LibTIFF source code and rebuild the software. This patch fixes the use-after-free vulnerability in the tiffmedian tool. Until the patch is applied, avoid processing untrusted or malformed TIFF files locally with the vulnerable versions of LibTIFF (up to 4.7.0) to reduce the risk of exploitation. [1]