Skip to content
Fencer Intel
high 7.8

CVE-2018-13875 json

An issue was discovered in the HDF HDF5 1.8.20 library.

published 8y ago modified 4mo ago also EUVD-2018-5809

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits
0
none known

Summary

An issue was discovered in the HDF HDF5 1.8.20 library. There is an out-of-bounds read in the function H5VM_memcpyvv in H5VM.c.

Is CVE-2018-13875 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-2018-13875 updated cvss 5.3

hdf5: out-of-bounds read in the function H5VM_memcpyvv in H5VM.c

  • Red Hat Enterprise Linux 8 hdf5 Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) hdf5 Red Hat OpenStack Platform 8 (Liberty) hdf5 Red Hat OpenStack Platform 9 (Mitaka) hdf5
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 10 (Newton) hdf5
    affected: no fix available “Fix deferred”
  • Red Hat OpenStack Platform 12 (Pike) hdf5
    affected: no fix available
  • Red Hat OpenStack Platform 13 (Queens) hdf5 Red Hat OpenStack Platform 14 (Rocky) hdf5
    affected: no fix available “Fix deferred”

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

0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/TeamSeri0us/pocs/tree/master/hdf5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/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

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.