Skip to content
Noroxi
CVE-2017-15104· NVD / CVE Program· CNA redhat

An access flaw was found in Heketi 5, where the heketi.json configuration file was world readable.

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Dec 18, 2017
Updated
Jun 16, 2026
EPSS
0.4% · 35th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

Affected systems

VendorProduct
heketi projectheketi
redhatenterprise linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • heketi project heketi5.0.0
  • redhat enterprise linux7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Heketi Heketi

    • 5.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/heketi/heketibefore 5.0.15.0.1
Gogithub.com/heketi/heketibefore 5.0.1+incompatible5.0.1+incompatible
Red Hat:storage:3.3:server:el7heketibefore 0:5.0.0-19.el7rhgs0:5.0.0-19.el7rhgs
Red Hat:storage:3.3:server:el7heketi-clientbefore 0:5.0.0-19.el7rhgs0:5.0.0-19.el7rhgs
Red Hat:storage:3.3:server:el7python-heketibefore 0:5.0.0-19.el7rhgs0:5.0.0-19.el7rhgs

Same product

heketi project: all records

Other highest-scoring records for the same primary product.

  • CVE-2017-15103A security-check flaw was found in the way the Heketi 5 server API handled user requests.
    37Monitor
  • CVE-2020-10763An information-disclosure flaw was found in the way Heketi before 10.1.0 logs sensitive information.
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/heketi/heketi5.0.1Package registry (OSV)
Go:github.com/heketi/heketi5.0.1+incompatiblePackage registry (OSV)
red hat:heketi0:5.0.0-19.el7rhgs · Red Hat:storage:3.3:server:el7Package registry (OSV)
red hat:heketi-client0:5.0.0-19.el7rhgs · Red Hat:storage:3.3:server:el7Package registry (OSV)
red hat:python-heketi0:5.0.0-19.el7rhgs · Red Hat:storage:3.3:server:el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-552 · Files or Directories Accessible to External Parties

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records