CVE-2024-29165
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 · uneditedHDF5 through 1.14.3 contains a buffer overflow in H5Z__filter_fletcher32, 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 confidenceA buffer overflow vulnerability exists in the H5Z__filter_fletcher32 function of the HDF5 library (versions through 1.14.3). The overflow corrupts the instruction pointer, enabling potential code execution or causing denial of service.
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< 1.14.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed HDF5 library versionRun 'h5dump -version' or check the library binary directly via 'strings libhdf5.so | grep -i version' or check your package manager for hdf5 package versionAffected if Version is lower than 1.14.4 (e.g., 1.14.3, 1.14.2, 1.14.1, 1.14.0, or any 1.1x.x version below 1.14.4)
-
Locate HDF5 library files on the systemSearch for libhdf5 files: 'find /usr -name "libhdf5*" 2>/dev/null' or check common install paths like /usr/lib, /usr/local/libAffected if Any libhdf5.so or libhdf5.a file found with version below 1.14.4 indicates the library is affected
-
Identify HDF5 files using fletcher32 filterUse 'h5dump -H <file.h5>' to inspect HDF5 file metadata and look for 'fletcher32' in the filter list, or use 'h5dump -pH <file.h5>' to see all dataset filter configurationsAffected if HDF5 files with fletcher32 checksum filter enabled are processed by the vulnerable H5Z__filter_fletcher32 function
Your environment is affected if the HDF5 library version is below 1.14.4 AND you use HDF5 files with fletcher32 checksum filter enabled
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.14.4
Upgrade HDF5 to version 1.14.4 or later to remediate this vulnerability; validate that dependent applications function correctly after the upgrade.
1.14.4
- 1. Identify the current HDF5 version installed by running: h5dump --version or pkg-config --modversion hdf5
- 2. Download HDF5 version 1.14.4 from the official HDF Group website at www.hdfgroup.org or their GitHub releases page
- 3. If building from source, extract the archive and run: ./configure --prefix=/usr/local/hdf5
- 4. Run make and make install to install the updated version
- 5. Ensure any applications or libraries dynamically linked to HDF5 are recompiled or relinked against the new version
- 6. Verify the upgrade by running: h5dump --version (should show 1.14.4 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29165 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-29165 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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