dbcve.org
Hdf5Application · Hdfgroup

CVE-2024-32618

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 Library through 1.14.3 contains a heap-based buffer overflow in H5T__get_native_type in H5Tnative.c, resulting in the corruption of the instruction pointer.

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

Heap-based buffer overflow in H5T__get_native_type function in H5Tnative.c allows corruption of the instruction pointer, potentially enabling arbitrary code execution. The vulnerability affects HDF5 Library versions through 1.14.3.

MitigationUpdate to patched HDF5 version when available; if immediate update not possible, restrict untrusted HDF5 file processing and monitor for anomalous behavior.

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. Check installed HDF5 library version
    Run 'h5dump --version' or check your package manager for installed hdf5 package version, or run 'pkg-config --modversion hdf5' if linked against the library
    Affected if Version is 1.14.3 or lower (any version before 1.14.4)
  2. Identify HDF5-linked applications
    Use 'ldd /path/to/binary' or 'ldconfig -p | grep hdf5' to find binaries that load the HDF5 library, or check process list for running applications using HDF5
    Affected if Any application is linked against a vulnerable HDF5 library version
  3. Verify HDF5 file processing capability
    Check if applications process HDF5 files from untrusted sources, or review application logs for HDF5 file operations (look for .h5, .hdf5, .hdf file extensions in file access patterns)
    Affected if Application reads or processes HDF5 files, especially from external or untrusted sources
  4. Inspect HDF5 data type handling
    Review application code or configuration for calls to datatype-related HDF5 functions, particularly H5Tget_native_type or similar type conversion operations
    Affected if Application performs datatype operations on HDF5 files (this triggers the vulnerable H5T__get_native_type function)

You are affected if HDF5 library version is below 1.14.4 AND your system processes HDF5 files, particularly from untrusted sources, using datatype-related operations.

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

Update to patched HDF5 version when available; if immediate update not possible, restrict untrusted HDF5 file processing and monitor for anomalous behavior.

Recommended fix High confidence

HDF5 1.14.4

  1. 1. Identify current HDF5 library version by running 'h5dump --version' or checking your application's linked library version
  2. 2. Download HDF5 version 1.14.4 or later from the official HDF Group website (www.hdfgroup.org)
  3. 3. Install the new version following the platform-specific build instructions (cmake/configure, make, make install)
  4. 4. Rebuild and reinstall any applications or tools that statically or dynamically link against the HDF5 library
  5. 5. Verify the fix by confirming the new version is 1.14.4 or later using 'h5dump --version'
  6. 6. Test that dependent applications function correctly with the updated library
Caveat Review the HDF5 1.14.4 release notes for any API/ABI changes; minor version upgrades within 1.14.x are typically backward compatible but verify application compatibility

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32618 — 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-32618 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