Process crash via recursive error-stack reporting
Published May 9, 2024 · Updated Feb 13, 2025
Uncontrolled recursion in The HDF Group HDF5 1.14.3 and earlier allows remote attackers to exhaust the process stack during error reporting. H5E__push_stack calls an error-producing reference increment for an invalid identifier; that failure invokes H5E_printf_stack again and recursively repeats the same path. Public sources do not identify the application operation or input that supplies the invalid identifier, so exposure depends on a caller reaching this error path.
Summary
What happened
Uncontrolled recursion in The HDF Group HDF5 1.14.3 and earlier allows remote attackers to exhaust the process stack during error reporting. H5E__push_stack calls an error-producing reference increment for an invalid identifier; that failure invokes H5E_printf_stack again and recursively repeats the same path. Public sources do not identify the application operation or input that supplies the invalid identifier, so exposure depends on a caller reaching this error path.
The record
- CVE
- CVE-2024-32609
- Published
- May 9, 2024
- Updated
- Feb 13, 2025
- Vendor
- The HDF Group
- Product
- HDF5
- Classifications
- CWE-674
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.14.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo