CVE-2019-9152 json
An issue was discovered in the HDF HDF5 1.10.4 library.
published 2019-02-25 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-18533
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
An issue was discovered in the HDF HDF5 1.10.4 library. There is an out of bounds read in the function H5MM_xstrdup in H5MM.c when called from H5O_dtype_decode_helper in H5Odtype.c.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-9152 updated cvss 5.3
hdf5: out of bounds read in function H5MM_xstrdup in H5MM.c
-
Red Hat OpenStack Platform 8 (Liberty) hdf5 Red Hat OpenStack Platform 9 (Mitaka) hdf5 Red Hat OpenStack Platform 10 (Newton) hdf5 Red Hat OpenStack Platform 13 (Queens) hdf5 Red Hat OpenStack Platform 14 (Rocky) hdf5 Red Hat OpenStack Platform 15 (Stein) hdf5affected: no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.49% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/magicSwordsMan/PAAFS/tree/master/vul8 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/magicSwordsMan/PAAFS/tree/master/vul8
exploit, third-party-advisory
Sources
- CVE List CVE-2019-9152
- NVD CVE-2019-9152
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.