dbcve.org
Hdf5Application · Hdfgroup

CVE-2024-32619

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_copy_reopen in H5T.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_copy_reopen function in H5T.c in HDF5 Library through 1.14.3 allows corruption of the instruction pointer, potentially enabling arbitrary code execution via specially crafted HDF5 files.

MitigationUpgrade HDF5 Library to version 1.14.4 or later. If immediate upgrade is not feasible, sanitize or reject untrusted HDF5 files before processing and disable datatype copy operations where possible.

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. Identify installed HDF5 library version
    Run 'h5dump --version' or check your package manager for hdf5 version, or inspect the library file libhdf5.so and check its version metadata
    Affected if version is below 1.14.4 (any version from 1.14.0 through 1.14.3, or unversioned builds)

Affected if HDF5 version is below 1.14.4 and untrusted HDF5 files are processed using H5Tcopy or similar datatype copy 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

Upgrade HDF5 Library to version 1.14.4 or later. If immediate upgrade is not feasible, sanitize or reject untrusted HDF5 files before processing and disable datatype copy operations where possible.

Recommended fix High confidence

1.14.4

  1. 1. Identify all applications and systems that link against the HDF5 library in your environment
  2. 2. Locate the currently installed HDF5 library version (typically found in /usr/lib, /usr/local/lib, or via pkg-config --modversion hdf5)
  3. 3. Consult your system's package manager or build system to obtain HDF5 version 1.14.4 or later
  4. 4. Upgrade the HDF5 library to version 1.14.4 or newer
  5. 5. Rebuild any applications statically linked against HDF5 to ensure they use the fixed library
  6. 6. Verify the new version is correctly installed and loaded (h5dump --version or similar tool can confirm)
  7. 7. Test that dependent applications function correctly with the upgraded library

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

Fix this in Hdf5 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation5.0 h
  • Testing5.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,390
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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