Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-17508

hdf5: Divide-by-zero in the H5T_set_loc function

Overview

Published
11 Dec 2017
Modified
17 Jun 2026
Medium CVE
0 Registry packages
2 OS packages
5 Linux distributions
Yes Fix available

Description

In HDF5 1.10.1, there is a divide-by-zero vulnerability in the function H5T_set_loc in the H5T.c file in libhdf5.a. For example, h5dump would crash when someone opens a crafted hdf5 file.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Weakness: CWE-369

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 10 fixes

Red Hat 1 release · 1 package

wont fix 1
hdf5
Red Hat fixes for CVE-2017-17508
ReleasePackageFixed in
7 hdf5 wont fix

debian 5 releases · 1 package

fixed 4 affected 1
hdf5
debian fixes for CVE-2017-17508
ReleasePackageFixed in
11 hdf5 1.10.4+repack-1
12 hdf5 1.10.4+repack-1
13 hdf5 1.10.4+repack-1
14 hdf5 1.10.4+repack-1
9 hdf5 affected

echo 1 release · 1 package

fixed 1
hdf5
echo fixes for CVE-2017-17508
ReleasePackageFixed in
hdf5 1.10.4+repack-1

root.io debian 2 releases · 1 package

fixed 2
rootio-hdf5
root.io debian fixes for CVE-2017-17508
ReleasePackageFixed in
11 rootio-hdf5 1.10.4+repack-1
12 rootio-hdf5 1.10.4+repack-1

ubuntu 1 release · 1 package

fixed 1
hdf5
ubuntu fixes for CVE-2017-17508
ReleasePackageFixed in
18.04-ESM hdf5 1.10.0-patch1+docs-4ubuntu0.1~esm1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.