Gluster StorageApplication · Redhat
CVE-2020-10763
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHeketi before version 10.1.0 contains an information-disclosure vulnerability where sensitive information such as gluster-block passwords are logged in plaintext. An attacker with local access to the Heketi server can read these log files to obtain credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Gluster StorageApplication
= 3.0= 3.5
Openshift Container PlatformApplication
= 4.0
Enterprise LinuxOperating system
= 7.0< 10.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Heketi installation and versionRun 'heketi --version' or check the package manager (rpm -q heketi or dpkg -l heketi) to determine the installed versionAffected if Installed version is earlier than 10.1.0
-
Locate Heketi log filesCheck common log locations such as /var/log/heketi/, /var/log/glusterfs/, or the configured log path in /etc/heketi/heketi.jsonAffected if Log files exist and are accessible to the user
-
Search log files for plaintext passwordsUse grep or search the log files for strings matching 'password', 'secret', or gluster-block related credentials in plaintext (e.g., grep -i 'password' /var/log/heketi/*.log)Affected if Log files contain any plaintext passwords or secrets related to gluster-block or storage credentials
-
Check if gluster-block is in useReview Heketi configuration and running environment for gluster-block volumes or block hosting (look for 'gluster-block' in configuration files or running processes)Affected if Gluster-block volumes are configured and being managed by Heketi
-
Verify local access to log filesCheck file permissions on identified log files to confirm if unprivileged local users can read them (ls -la /var/log/heketi/ or equivalent path)Affected if Log files have overly permissive read access (world-readable or accessible by non-admin users)
A system is affected if Heketi version is earlier than 10.1.0 AND gluster-block is in use AND log files contain plaintext credentials accessible to the user.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data10.1.0
Upgrade Heketi to version 10.1.0 or later. Additionally, restrict local access to the server and audit/clear existing log files that may contain exposed credentials.
Fix this in Gluster Storage
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10763 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-10763 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data