dbcve.org
Hdf5Application · Hdfgroup

CVE-2024-32614

HIGH · 8.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 1.14.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 H5VM_memcpyvv in H5VM.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 · moderate confidence

A segmentation fault (SEGV) vulnerability exists in the H5VM_memcpyvv function within H5VM.c in HDF5 Library versions through 1.14.3. This appears to be a memory copy operation flaw that can cause a denial of service or potentially enable code execution when processing specially crafted HDF5 files.

MitigationUpdate HDF5 Library to the latest version once available, or apply any security patches released by the HDF5 maintainers. Validate HDF5 file inputs before processing and restrict processing of untrusted HDF5 files in vulnerable deployments.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify HDF5 library installation
    Run 'h5dump --version' or 'h5ls --version' to display the HDF5 library version. If these tools are not available, check for libhdf5.so or libhdf5.dylib files and query their version using 'strings libhdf5.so | grep -i version' or checking package metadata with 'dpkg -l libhdf5' (Debian) or 'rpm -qi hdf5' (RHEL).
    Affected if The installed HDF5 library version is 1.14.3 or earlier (any version below 1.14.4).
  2. Confirm HDF5 development package version
    If HDF5 was built from source, check the H5public.h header file for the H5_VERSION_NUM macro defining the version number. For package-managed installations, query the installed package directly.
    Affected if The version macro or package version shows a number less than 1.14.4.
  3. Identify processes or applications using HDF5
    Locate any applications or scripts that link against libhdf5 by running 'ldd <executable>' on suspected binaries or searching for dependencies with 'grep -r libhdf5 /proc/<pid>/maps' for running processes.
    Affected if Any application linked against a vulnerable HDF5 library version is in use.
  4. Assess exposure to untrusted HDF5 files
    Review whether any HDF5-processing application in the environment accepts input from untrusted sources, network uploads, or user-provided files without prior validation.
    Affected if Applications process HDF5 files from untrusted or external sources using a vulnerable library version.

You are affected if the installed HDF5 library version is below 1.14.4 and any application using that library processes HDF5 files, especially 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 the latest version once available, or apply any security patches released by the HDF5 maintainers. Validate HDF5 file inputs before processing and restrict processing of untrusted HDF5 files in vulnerable deployments.

Recommended fix Moderate confidence

HDF5 1.14.4

  1. 1. Identify the current HDF5 library version in your environment using 'h5dump --version' or checking your package manager
  2. 2. If running a version prior to 1.14.4, plan for upgrade during a maintenance window
  3. 3. Backup any existing HDF5 files and configurations
  4. 4. Obtain HDF5 1.14.4 or later from the official source at www.hdfgroup.org or your distribution's package manager
  5. 5. Install the new version following your platform's standard build or installation process
  6. 6. Verify the installation by running 'h5dump --version' to confirm version 1.14.4 or later is active
  7. 7. Test that your applications using HDF5 function correctly with the new library
Caveat No specific breaking changes documented in the provided reference material; standard regression testing recommended

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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