Hdf5Application · Hdfgroup

CVE-2024-29163

HIGH · 7.4 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 1.14.4 or later.
See remediation →
79/100
Remediation priority · High
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 through 1.14.3 contains a heap buffer overflow in H5T__bit_find, resulting in the corruption of the instruction pointer and causing denial of service or potential code execution.

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

HDF5 library through 1.14.3 contains a heap buffer overflow vulnerability in the H5T__bit_find function. This memory corruption issue can corrupt the instruction pointer, leading to denial of service or potentially allowing arbitrary code execution.

MitigationUpgrade HDF5 to version 1.14.4 or later which contains the security fix. If immediate patching is not possible, consider restricting access to untrusted HDF5 files until the upgrade can be performed.

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
Local
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate the HDF5 library installation
    Run 'find /usr -name "libhdf5*" 2>/dev/null' or check your package manager (dpkg -l | grep hdf5, rpm -qa | grep hdf5, brew list hdf5)
    Affected if HDF5 library files are present on the system
  2. Determine the installed HDF5 version
    Run 'h5dump --version' or check the library file version with 'ldd --version' or examine the library binary directly with strings/hexdump looking for version strings
    Affected if The version displayed is 1.14.3 or earlier (any version below 1.14.4)
  3. Verify the H5T__bit_find function is present
    Check that the HDF5 library is compiled and includes the H5T (HDF5 datatype) functions - this is typically present in standard builds. Use 'nm -D libhdf5.so | grep H5T_bit_find' if the library is accessible
    Affected if The library contains the vulnerable H5T__bit_find function and the version is < 1.14.4
  4. Check for untrusted HDF5 file processing
    Review any applications or scripts that process HDF5 files, particularly those that may receive files from untrusted sources or perform datatype bit operations
    Affected if Your applications load and process HDF5 files and the library version is < 1.14.4

You are affected if your installed HDF5 library version is below 1.14.4 and you process HDF5 files using the H5T__bit_find functionality.

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 to version 1.14.4 or later which contains the security fix. If immediate patching is not possible, consider restricting access to untrusted HDF5 files until the upgrade can be performed.

Recommended fix High confidence

1.14.4

  1. Check the current HDF5 version installed in your environment
  2. Download HDF5 version 1.14.4 from the official HDF Group website (www.hdfgroup.org)
  3. Extract the downloaded archive
  4. Configure the build with appropriate options for your system (e.g., ./configure --prefix=/path/to/install)
  5. Compile HDF5 (make)
  6. Install the compiled version (make install)
  7. Rebuild any applications or libraries that depend on HDF5 against the new version
  8. Verify the installation by checking the HDF5 version matches 1.14.4
Caveat Minor version upgrades typically maintain backward compatibility, but test your specific use cases

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

Fix this in Hdf5 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-29163 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