Skip to content
Fencer Intel
medium 6.5

CVE-2019-8398 json

An issue was discovered in the HDF HDF5 1.10.4 library.

published 7y ago modified 4mo ago also EUVD-2019-17788

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
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 H5T_get_size in H5T.c.

Patch / fix

  • hdf5 Debian 14, Debian 13 1.14.5+repack-1

debian advisories DEBIAN-CVE-2019-8398

  • hdf5 Arch Linux 1.10.5-1

arch linux advisories AVG-901

Is CVE-2019-8398 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-8398 updated cvss 5.5

hdf5: Out-of-Bounds Read in function H5T_get_size in H5T.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) hdf5
    affected: 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.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/magicSwordsMan/PAAFS/tree/master/vul6 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel 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.