dbcve.org
Gluster BlockApplication · Redhat

CVE-2020-10762

MEDIUM · 5.5 CVSS v3.1 Published 2020-11-24
Fix available
A fix is available. Upgrade to 0.5.1 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
An information-disclosure flaw was found in the way that gluster-block before 0.5.1 logs the output from gluster-block CLI operations. This includes recording passwords to the cmd_history.log file which is world-readable. This flaw allows local users to obtain sensitive information by reading the log file. The highest threat from this vulnerability is to data confidentiality.

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 confidence

gluster-block before version 0.5.1 writes CLI operation output including passwords to cmd_history.log, which is world-readable, allowing local users to read sensitive authentication credentials from the log file.

MitigationUpgrade to gluster-block 0.5.1 or later, and remediate existing installations by restricting cmd_history.log permissions and purging any recorded passwords.

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 BlockApplication
Affected:< 0.5.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed gluster-block version
    Run 'gluster-block --version' or query the RPM package: 'rpm -q gluster-block'
    Affected if Version is lower than 0.5.1
  2. Locate the cmd_history.log file
    Search for cmd_history.log in common paths such as /var/log/gluster-block/, /var/log/, or run 'find /var -name cmd_history.log 2>/dev/null'
    Affected if The log file exists in a world-readable location
  3. Verify cmd_history.log permissions are world-readable
    Run 'ls -la <path_to_cmd_history.log>' and check if permissions include 'r--r--r--' (644) or 'rwxr-xr-x' (755)
    Affected if The file is readable by all users (others have read permission)
  4. Inspect log contents for password patterns
    Run 'grep -i password <path_to_cmd_history.log>' or view the file contents with 'cat'
    Affected if Plaintext passwords or sensitive authentication credentials appear in the log

A user is affected if gluster-block version is below 0.5.1 AND the cmd_history.log file exists with world-readable permissions containing sensitive credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 0.5.1 or later
Fixed in 0.5.1
Interim mitigation

Upgrade to gluster-block 0.5.1 or later, and remediate existing installations by restricting cmd_history.log permissions and purging any recorded passwords.

Fix this in Gluster Block Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10762 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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