dbcve.org
Hdf5Application · Hdfgroup

CVE-2024-32609

HIGH · 7.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 1.14.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HDF5 Library through 1.14.3 allows stack consumption in the function H5E_printf_stack in H5Eint.c.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The HDF5 Library through version 1.14.3 contains a stack consumption vulnerability in the H5E_printf_stack function in H5Eint.c. The function, responsible for error message formatting and printing, can be triggered with specially crafted input to cause excessive stack consumption, potentially leading to stack exhaustion and denial of service.

MitigationUpgrade HDF5 Library to a version beyond 1.14.3 once the patch is available. Until then, limit exposure to untrusted HDF5 files or inputs that trigger extensive error reporting.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hdf5Application
Affected:< 1.14.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Detect if HDF5 library is installed
    Search for HDF5 library files: on Linux/Unix run 'find /usr -name "*hdf5*" 2>/dev/null' or check package manager (dpkg -l | grep hdf5, rpm -qa | grep hdf5). On Windows, check Program Files for HDF5 directories or search for hdf5.dll/hdf5.lib
    Affected if No HDF5 installation found means not affected
  2. Identify installed HDF5 version
    Run 'h5dump --version' or 'h5ls --version' if HDF5 command line tools are installed. Alternatively, check library version directly: 'ldconfig -p | grep hdf5' to find the library path, then check the file version or use 'strings' on the library to find version strings
    Affected if Version cannot be determined means status is unknown; proceed to check available version information from package manager or software that bundles HDF5
  3. Compare version to affected range
    If version was found, verify it is less than 1.14.4 (affected) or >= 1.14.4 (not affected). Check package manager output for version: 'apt list --installed 2>/dev/null | grep -i hdf5' or 'pip list | grep -i hdf5' for Python bindings
    Affected if Installed version is < 1.14.4 indicates the environment contains the vulnerable library
  4. Check if applications use HDF5 and process external input
    Identify applications or scripts that load HDF5 files from untrusted sources. Search codebases for 'h5open', 'h5fopen', 'H5Fopen' or similar HDF5 API calls. Review whether these applications process files from users, network, or untrusted sources
    Affected if HDF5 < 1.14.4 is present AND applications process untrusted HDF5 files means the vulnerability is potentially exploitable

Environment is affected if HDF5 Library version is below 1.14.4 AND the library processes or can process HDF5 files from untrusted sources that could trigger the error reporting path in H5E_printf_stack.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.14.4 or later
Fixed in 1.14.4
Interim mitigation

Upgrade HDF5 Library to a version beyond 1.14.3 once the patch is available. Until then, limit exposure to untrusted HDF5 files or inputs that trigger extensive error reporting.

Recommended fix High confidence

HDF5 1.14.4

  1. 1. Identify the current HDF5 installation and version (e.g., `h5dump --version` or check package manager)
  2. 2. Download HDF5 version 1.14.4 from the official HDF Group website (www.hdfgroup.org) or trusted package repositories
  3. 3. If using a package manager (apt, yum, brew, conda, etc.), upgrade to version 1.14.4 or later
  4. 4. If building from source, download the 1.14.4 source from the official site, configure, compile, and install following standard build procedures
  5. 5. Verify the upgrade was successful by checking the version (e.g., `h5dump --version`)
  6. 6. Test that applications depending on HDF5 function correctly with the new version
Caveat Minor version upgrades may include API/ABI changes; review the HDF5 1.14.4 release notes for any backward-incompatible changes that may affect dependent applications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hdf5 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32609 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-32609 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data