dbcve.org
Hdf5Application · Hdfgroup

CVE-2024-32607

MEDIUM · 5.7 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 1.14.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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 has a SEGV in H5A__close in H5Aint.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 · moderate confidence

HDF5 Library through version 1.14.3 contains a NULL pointer dereference or similar memory corruption issue in the H5A__close function (in H5Aint.c) that causes a segmentation fault and corrupts the instruction pointer. This occurs during attribute close operations, likely when processing malformed HDF5 files with specific attribute structures.

MitigationUpdate HDF5 Library to a version beyond 1.14.3 when patches become available. Until then, avoid processing untrusted or potentially malformed HDF5 files in vulnerable applications.

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
None
Integrity
Low
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/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 'h5ls --version' to display the HDF5 version. On Linux, also check '/usr/lib/x86_64-linux-gnu/libhdf5.so*' version strings via 'strings' or check package manager with 'dpkg -l libhdf5*' or 'rpm -qa | grep hdf5'. On macOS, use 'brew list hdf5' or check via 'otool -L' on library files.
    Affected if The reported version is 1.14.3 or earlier (any version below 1.14.4).
  2. Identify applications using HDF5
    Search for binaries or scripts that link to HDF5: 'ldconfig -p | grep hdf5' (Linux), 'otool -L /path/to/binary | grep hdf5' (macOS), or 'dumpbin /dependents' (Windows). Also scan for Python packages with 'pip list | grep -i hdf5' or R packages with 'installed.packages()["rhdf5",]'.
    Affected if Any application using HDF5 library version below 1.14.4 is potentially affected when processing untrusted HDF5 files.
  3. Locate HDF5 shared libraries on the system
    Use 'find /usr -name "*hdf5*" -type f 2>/dev/null' (Linux) or 'mdfind "kMDItemFSName == *hdf5*"' (macOS) to find HDF5 library files. Check version info embedded in binaries with 'file' or via version resource viewers.
    Affected if HDF5 library files exist with version strings indicating build versions below 1.14.4.
  4. Audit HDF5 file processing workflows
    Review application logs, data ingestion pipelines, or user-upload workflows that process .h5 or .hdf5 files. Identify which tools, scripts, or services handle these files and note their HDF5 library dependency.
    Affected if Any system component that parses, opens, or validates HDF5 files from untrusted sources using a vulnerable HDF5 version is at risk of triggering the NULL pointer dereference.

The environment is affected if HDF5 Library version 1.14.3 or earlier is installed AND any application or workflow processes potentially malformed HDF5 files from untrusted sources.

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 HDF5 Library to a version beyond 1.14.3 when patches become available. Until then, avoid processing untrusted or potentially malformed HDF5 files in vulnerable applications.

Recommended fix High confidence

1.14.4

  1. 1. Identify the current HDF5 library version installed in your system using 'h5dump --version' or checking your package manager
  2. 2. Download HDF5 version 1.14.4 from the official HDF Group website (www.hdfgroup.org) or your system's package repository
  3. 3. Install HDF5 1.14.4 by following the standard build process: ./configure, make, make install OR use your system's package manager to update
  4. 4. Rebuild and recompile any applications that depend on the HDF5 library to link against the new version
  5. 5. Test your applications to ensure functionality is preserved after the upgrade
  6. 6. Verify the fix by confirming the version is 1.14.4 or later

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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