Skip to content
Fencer Vulns
high 7.8

CVE-2017-15104 json

Information Exposure in Heketi

published 2017-12-18 8 y ago modified 2026-06-17 4 mo ago also GHSA-q9vw-wr57-xjv3 , GO-2022-0866 , EUVD-2022-1147

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

Summary

An access flaw was found in Heketi 5, where the heketi.json configuration file was world readable. An attacker having local access to the Heketi server could read plain-text passwords from the heketi.json file.

Patch / fix

  • go github.com/heketi/heketi 5.0.1, 5.0.1+incompatible
  • heketi storage 3.3 5.0.0-19.el7rhgs
  • heketi-client storage 3.3 5.0.0-19.el7rhgs
  • python-heketi storage 3.3 5.0.0-19.el7rhgs

red hat advisories RHSA-2017:3481

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-2017-15104 updated cvss 5.5

heketi: Information disclosure through world readable file

  • Red Hat Gluster Storage Server 3.3 on RHEL-7 heketi 5.0.0-19.el7rhgs, heketi-client 5.0.0-19.el7rhgs, python-heketi 5.0.0-19.el7rhgs
    fixed: vendor fix RHSA-2017:3481

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.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/heketi/heketi
<5.0.1
<5.0.1+incompatible
5.0.1
5.0.1+incompatible

Affected products

  • Heketi Heketi

Classification

Weakness
  • CWE-552 Files or Directories Accessible to External Parties
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

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.