GHSA-rm7c-x6gj-2mr8 is a medium-severity (CVSS 5.5) CWE-532 vulnerability in github.com/heketi/heketi. A fix is available for github.com/heketi/heketi — see the affected versions and patch details below.
Heketi logs sensitive information
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-rm7c-x6gj-2mr8 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/heketi/heketiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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 potentially sensitive information such as gluster-block passwords.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/heketi/heketi | all versions | 10.1.0go get github.com/heketi/heketi@v10.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/heketi/heketi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/heketi/heketi to 10.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rm7c-x6gj-2mr8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rm7c-x6gj-2mr8 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-rm7c-x6gj-2mr8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The version of heketi shipped with Red Hat Gluster Storage 3 does not filter out gluster-block volume passwords, hence affected by this vulnerability.
| Product | Fixed in | Advisory |
|---|---|---|
| Native Client for RHEL 7 for Red Hat Storage | heketi-0:9.0.0-9.5.el7rhgs | RHSA-2020:4143 |
| Red Hat OpenShift Container Platform 4.7 | openshift4/ose-cluster-autoscaler:v4.7.0-202102130115.p0 | RHSA-2020:5633 |
Frequently Asked Questions
Is GHSA-rm7c-x6gj-2mr8 in your dependencies?
O3 Security finds GHSA-rm7c-x6gj-2mr8 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.