Heketi Project maintains a container storage orchestration tool designed to dynamically provision and manage Gluster storage volumes in Kubernetes environments, addressing a focused use case within cloud-native infrastructure. Its vulnerability surface centers on the core Heketi product and recurs through weaknesses including authentication bypass, sensitive-information exposure, inadequate access controls on files and directories, input-validation gaps, and OS command injection, patterns typical of management APIs that bridge container platforms and storage systems. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Heketi Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2019-3899CRITICAL It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse. This isue only affects heketi as ship | Apr 22, 2019 | 9.8 | 30 | NO | NO |
CVE-2017-15103HIGH A security-check flaw was found in the way the Heketi 5 server API handled user requests. An authenticated Heketi user could send specially crafted requests to the Heketi server, r | Dec 18, 2017 | 8.8 | 29 | NO | NO |
CVE-2017-15104HIGH 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 passwo | Dec 18, 2017 | 7.8 | 24 | NO | NO |
CVE-2020-10763MEDIUM An information-disclosure flaw was found in the way Heketi before 10.1.0 logs sensitive information. This flaw allows an attacker with local access to the Heketi server to read pot | Nov 24, 2020 | 5.5 | 16 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Heketi Project.
Media articles that mention a CVE ID that affects a product developed by Heketi Project — matched by CVE ID, not by vendor name.