CVE-2024-29159
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_scaleoffset, 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 · moderate confidenceHDF5 library versions through 1.14.3 contain a buffer overflow vulnerability in the H5Z__filter_scaleoffset compression filter. The overflow allows corruption of the instruction pointer, enabling denial of service via crash or potentially arbitrary code execution.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Check installed HDF5 versionRun 'h5dump --version' or check the library file version (e.g., libhdf5.so.100) to determine the exact version numberAffected if Version is below 1.14.4 (including any 1.14.x version through 1.14.3)
-
Identify scaleoffset filter usage in HDF5 filesUse 'h5dump -H <file.h5>' to inspect HDF5 datasets and look for references to the scaleoffset filter, or search HDF5 application code for calls to H5Pset_scaleoffsetAffected if Any HDF5 file or application uses the scaleoffset compression filter on datasets
-
Verify scaleoffset filter is enabled in HDF5 buildCheck HDF5 configuration with 'h5dump -V' or examine the HDF5 plugin directory for the scaleoffset filter module (filter ID 305)Affected if The scaleoffset filter is compiled and available in the HDF5 installation
You are affected if HDF5 version is below 1.14.4 AND the scaleoffset compression filter is actively used in your HDF5 files or applications.
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. If immediate patching is not possible, disable or avoid using the scaleoffset filter in HDF5 applications until the patch can be applied.
1.14.4
- Identify the current HDF5 version installed in your environment using 'h5dump --version' or 'pkg-config --modversion hdf5'
- Visit www.hdfgroup.org to download HDF5 version 1.14.4
- If using a package manager (apt, yum, brew, conda, etc.), update to version 1.14.4 or the latest available version that includes this fix
- For source compilation: download hdf5-1.14.4.tar.gz from www.hdfgroup.org, extract, configure, compile, and install
- Verify the new version is active by running 'h5dump --version' again
- Test any applications that depend on HDF5 to ensure functionality is maintained
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29159 — 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-29159 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