Filtered by vendor Hdfgroup
Subscribe
Total
66 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2017-17506 | 1 Hdfgroup | 1 Hdf5 | 2024-02-28 | 4.3 MEDIUM | 6.5 MEDIUM |
| In HDF5 1.10.1, there is an out of bounds read vulnerability in the function H5Opline_pline_decode in H5Opline.c in libhdf5.a. For example, h5dump would crash when someone opens a crafted hdf5 file. | |||||
| CVE-2017-17505 | 1 Hdfgroup | 1 Hdf5 | 2024-02-28 | 4.3 MEDIUM | 6.5 MEDIUM |
| In HDF5 1.10.1, there is a NULL pointer dereference in the function H5O_pline_decode in the H5Opline.c file in libhdf5.a. For example, h5dump would crash when someone opens a crafted hdf5 file. | |||||
| CVE-2016-4332 | 1 Hdfgroup | 1 Hdf5 | 2024-02-28 | 6.9 MEDIUM | 8.6 HIGH |
| The library's failure to check if certain message types support a particular flag, the HDF5 1.8.16 library will cast the structure to an alternative structure and then assign to fields that aren't supported by the message type and the library will write outside the bounds of the heap buffer. This can lead to code execution under the context of the library. | |||||
| CVE-2016-4331 | 1 Hdfgroup | 1 Hdf5 | 2024-02-28 | 6.9 MEDIUM | 8.6 HIGH |
| When decoding data out of a dataset encoded with the H5Z_NBIT decoding, the HDF5 1.8.16 library will fail to ensure that the precision is within the bounds of the size leading to arbitrary code execution. | |||||
| CVE-2016-4330 | 1 Hdfgroup | 1 Hdf5 | 2024-02-28 | 6.9 MEDIUM | 8.6 HIGH |
| In the HDF5 1.8.16 library's failure to check if the number of dimensions for an array read from the file is within the bounds of the space allocated for it, a heap-based buffer overflow will occur, potentially leading to arbitrary code execution. | |||||
| CVE-2016-4333 | 1 Hdfgroup | 1 Hdf5 | 2024-02-28 | 6.9 MEDIUM | 8.6 HIGH |
| The HDF5 1.8.16 library allocating space for the array using a value from the file has an impact within the loop for initializing said array allowing a value within the file to modify the loop's terminator. Due to this, an aggressor can cause the loop's index to point outside the bounds of the array when initializing it. | |||||