Storage ConsoleApplication · Redhat
CVE-2016-7062
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 · uneditedrhscon-ceph in Red Hat Storage Console 2 x86_64 and Red Hat Storage Console Node 2 x86_64 allows local users to obtain the password as cleartext.
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 · moderate confidenceThe rhscon-ceph component in Red Hat Storage Console 2 stores or exposes user passwords in cleartext, allowing any local user on the system to retrieve credentials. This is a local privilege escalation vulnerability where proper access controls or encryption are not applied to password storage or display mechanisms.
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
Storage ConsoleApplication
= 2.0
Storage Console NodeApplication
= 2.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
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 if Red Hat Storage Console 2.0 is installedCheck installed packages using 'rpm -qa | grep -i rhscon' or 'rpm -qa | grep -i storage-console' to locate the rhscon-ceph or console packagesAffected if The installed version matches 2.0 for Redhat Storage Console or Redhat Storage Console Node
-
Locate configuration files that may store credentialsSearch common config directories (/etc/rhscon, /etc/ceph, /opt/rh or similar paths) for files that may contain password entries - look for patterns like 'password', 'cephx', or 'keyring' in config filesAffected if Configuration files exist that contain cleartext passwords or credential strings
-
Check file permissions on credential storage locationsRun 'ls -la' on directories containing password or key files (check /etc/ceph/, /etc/rhscon/, or similar) and verify that permissions restrict read access to privileged users onlyAffected if Password or key files are readable by non-privileged local users (permissions show 'r--r--r--' or similar world-readable settings)
-
Search for cleartext passwords in application logsSearch log directories (/var/log/rhscon*, /var/log/ceph*) for plaintext password strings using 'grep -r "password" /var/log/' or similar search patternsAffected if Log files contain cleartext password entries or credential strings
A user is affected if Red Hat Storage Console or Storage Console Node version 2.0 is installed AND cleartext passwords are found in configuration files, or password files have overly permissive read permissions allowing any local user to retrieve credentials.
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 dataImplement secure credential storage mechanisms such as encrypted password hashing, restrict file/command access to password data, and ensure passwords are never written to logs, configuration files, or terminal output in plaintext.
Fix this in Storage Console
Scoped from the published advisory
- Consultation6.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7062 — 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-2016-7062 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