A heap-based buffer overflow in H5VM_array_fill() in src/H5VM.c in HDF5 before 2.2.0 lets a remote attacker cause an application crash and possibly execute arbitrary code with a crafted HDF5 file. When a dataset's unallocated chunks are read, H5D__fill_init() fills the fill-value buffer from datatype and dataspace metadata in the file. If that metadata is inconsistent with the buffer's allocated size, the write goes past the end of the buffer. The attacker can control the content written through the fill value stored in the file.

A heap-based buffer overflow in H5VM_array_fill() in src/H5VM.c in HDF5 before 2.2.0 lets a remote attacker cause an application crash and possibly execute arbitrary code with a crafted HDF5 file. When a dataset's unallocated chunks are read, H5D__fill_init() fills the fill-value buffer from datatype and dataspace metadata in the file. If that metadata is inconsistent with the buffer's allocated size, the write goes past the end of the buffer. The attacker can control the content written through the fill value stored in the file.

hdf5: HDF5: Denial of service via crafted HDF5 file hdf5: HDF5: Information disclosure and denial of service via crafted HDF5 file hdf5: HDF5: Denial of Service via integer underflow in Fletcher32 filter hdf5: HDF5: Denial of Service via crafted file in scale-offset filter hdf5: hdf5: Arbitrary code execution via heap-based buffer overflow

Affected: Ubuntu:Pro:14.04:LTS: hdf5, Ubuntu:Pro:16.04:LTS: hdf5, Ubuntu:Pro:18.04:LTS: hdf5, Ubuntu:Pro:20.04:LTS: hdf5, Ubuntu:20.04:LTS: r-bioc-rhdf5lib, Ubuntu:22.04:LTS: hdf5, Ubuntu:22.04:LTS: r-bioc-rhdf5lib, Ubuntu:24.04:LTS: hdf5, Ubuntu:24.04:LTS: r-bioc-rhdf5lib, Ubuntu:26.10: hdf5 and 3 more

A heap-based buffer overflow in H5VM_array_fill() in src/H5VM.c in HDF5 before 2.2.0 lets a remote attacker cause an application crash and possibly execute arbitrary code with a crafted HDF5 file. When a dataset's unallocated chunks are read, H5D__fill_init() fills the fill-value buffer from datatype and dataspace metadata in the file. If that metadata is inconsistent with the buffer's allocated size, the write goes past the end of the buffer. The attacker can control the content written through the fill value stored in the file.