CVE-2025-6857
BaseFortify
Publication date: 2025-06-29
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 |
|---|---|---|
| hdfgroup | hdf5 | 1.14.6 |
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-6857 is a stack-based buffer overflow vulnerability in the HDF5 library version 1.14.6. It occurs in the function H5G__node_cmp3 due to uncontrolled recursion triggered by specially crafted input, causing excessive recursive calls that overflow the stack. This overflow can lead to application crashes or denial of service by corrupting the stack memory during node comparisons in B-tree structures. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can cause denial of service (DoS) by crashing the application using the affected HDF5 library. An attacker with local access can exploit the stack overflow by providing crafted inputs that trigger deep recursion, leading to application instability and unavailability. There is no indication of remote exploitation or direct impact on confidentiality or integrity. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by building the HDF5 library with sanitizers enabled (such as AddressSanitizer) and running fuzz testing using the OSS-Fuzz harness 'h5_extended_fuzzer.c'. The stack overflow is detected during execution by AddressSanitizer when the vulnerable function is triggered. Specific commands would include compiling HDF5 with AddressSanitizer flags and running the fuzzing harness to observe crashes or stack overflows. For example, compile with: `clang -fsanitize=address -g -o h5_extended_fuzzer h5_extended_fuzzer.c` and then run `./h5_extended_fuzzer` to detect the issue. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding the use of the affected HDF5 version 1.14.6 or replacing the vulnerable component with an alternative product. Since no known countermeasures or patches are currently identified, restricting local access to trusted users only and monitoring for exploitation attempts is advised. Additionally, consider applying runtime protections such as stack canaries or AddressSanitizer during development and testing to detect exploitation attempts early. [3]