CVE-2020-26199
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 · uneditedDell EMC Unity, Unity XT, and UnityVSA versions prior to 5.0.4.0.5.012 contain a plain-text password storage vulnerability. A user credentials (including the Unisphere admin privilege user) password is stored in a plain text in multiple log files. A local authenticated attacker with access to the log files may use the exposed password to gain access with the privileges of the compromised user.
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 confidencePlain-text password storage vulnerability in Dell EMC Unity, Unity XT, and UnityVSA allows user credentials (including Unisphere admin) to be stored in plaintext within multiple log files. A local authenticated attacker with log file access can retrieve exposed passwords and gain unauthorized access with the compromised user's privileges.
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< 5.0.4.0.5.012< 5.0.4.0.5.012< 5.0.4.0.5.012CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 the installed Unity product versionAccess the Unisphere management interface or use the 'uemcli -sys version' command to retrieve the operating environment versionAffected if The version number is lower than 5.0.4.0.5.012 (for Unity, Unity XT, or UnityVSA)
-
Determine if log file access existsVerify that log files on the system are accessible to local authenticated users. Check file system permissions on typical log directories such as /var/log, /logs, or product-specific log locationsAffected if Local authenticated users can read system log files
-
Search log files for plaintext password patternsUse grep or similar tools to search log directories for patterns matching passwords: look for strings containing 'password=' or 'pwd=' or credential-related keywords in plain textAffected if Log files contain plaintext strings matching credential patterns
-
Inspect Unisphere access logs for credential leakageExamine Unisphere-related log files for entries containing the string 'password' or authentication credentials that appear in plaintext rather than hashed or maskedAffected if Unisphere or related service logs contain visible password strings
A system is affected if it runs a Dell EMC Unity, Unity XT, or UnityVSA version prior to 5.0.4.0.5.012 AND has log files that can be accessed by local authenticated users containing plaintext 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 data5.0.4.0.5.012
Apply vendor patch (version 5.0.4.0.5.012 or later) to remediate the vulnerability. Additionally, rotate all credentials that may have been exposed in logs and restrict access to system log files to prevent further exposure.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26199 — 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-26199 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