h5wasm is vulnerable to Heap-based Buffer Overflow
66
Medium Risk
A specially crafted H5T_VLEN dataset can cause Dataset.slice() to corrupt heap memory and abort the WASM runtime when slicing datasets with more than one element. The issue happens because the read path allocates memory only for the selected slice, but the reclaim logic mistakenly treats the buffer as if it contained the full dataset extent, causing invalid frees beyond the allocated buffer. Whole-dataset reads are not affected because their buffer size matches the full dataset. An attacker might exploit this by supplying a malicious HDF5 file containing a variable-length dataset and triggering a slice operation, causing a denial of service through runtime aborts and potentially opening the door to memory corruption impacts depending on allocator state.
You are affected if you are using a version that falls within the vulnerable range.
h5wasm is vulnerable to Heap-based Buffer Overflow in versions 0.7.6 - 0.10.2.
Upgrade the h5wasm library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

SOC 2Compliant
ISO 27001Compliant