CVE-2020-26197
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 PowerScale OneFS 8.1.0 - 9.1.0 contains an LDAP Provider inability to connect over TLSv1.2 vulnerability. It may make it easier to eavesdrop and decrypt such traffic for a malicious actor. Note: This does not affect clusters which are not relying on an LDAP server for the authentication provider.
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 Dell PowerScale OneFS LDAP provider has an implementation flaw preventing proper TLSv1.2 negotiation for LDAP authentication traffic. This forces the use of weaker TLS versions (TLS 1.0/1.1) or fallback to plaintext, enabling malicious actors to potentially eavesdrop on and decrypt authentication credentials transmitted between the cluster and LDAP server.
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= 8.1.0= 8.1.1= 8.1.2= 8.2.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 your PowerScale OneFS versionRun the command `isi version` or `isi get -V` on the cluster CLI to retrieve the installed OneFS version numberAffected if The displayed version matches exactly 8.1.0, 8.1.2, 8.1.2, or 8.2.2
-
Confirm LDAP authentication is configuredRun `isi auth ldap` to list configured LDAP providers. If no LDAP providers are shown, the system is not using LDAP authenticationAffected if One or more LDAP providers are listed and actively configured for authentication
-
Verify the TLS version in use for LDAPCheck the LDAP provider configuration for the TLS version setting. On OneFS, you can inspect this via the web UI under Access > Authentication > LDAP, or check the output of `isi auth ldap view <provider_name>` for TLS protocol settingsAffected if The configuration shows TLS 1.0, TLS 1.1, or indicates no TLS (plaintext LDAP) is being used for the LDAP connection
-
Review LDAP connection logs for TLS negotiation failuresExamine OneFS audit or authentication logs for events related to LDAP bind failures or TLS negotiation issues. You can use `isi auth logs` or check the /var/log/ directory for authentication eventsAffected if Logs indicate repeated TLS negotiation failures or fallback to non-TLS connections for LDAP traffic
You are affected only if your PowerScale OneFS version is exactly 8.1.0, 8.1.1, 8.1.2, or 8.2.2 AND you have LDAP authentication configured, and the LDAP connection is using TLS 1.0, TLS 1.1, or no encryption.
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 dataApply vendor-supplied patches for Dell PowerScale OneFS 9.2.0 or later to enable proper TLSv1.2 enforcement. Clusters not using LDAP for authentication are unaffected and require no action.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26197 — 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-26197 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