dbcve.org
Emc Powerscale OnefsOperating system · Dell

CVE-2020-26191

HIGH · 7.8 CVSS v3.1 Published 2021-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Dell EMC PowerScale OneFS versions 8.1.0 - 9.1.0 contain a privilege escalation vulnerability. A user with ISI_PRIV_JOB_ENGINE may use the PermissionRepair job to grant themselves the highest level of RBAC privileges thus being able to read arbitrary data, tamper with system software or deny service to users.

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

Dell EMC PowerScale OneFS versions 8.1.0-9.1.0 contain a privilege escalation vulnerability where a user with the ISI_PRIV_JOB_ENGINE privilege can exploit the PermissionRepair job to elevate themselves to the highest RBAC privilege level, allowing unauthorized read access to arbitrary data, system software tampering, or denial of service.

MitigationRestrict or audit the ISI_PRIV_JOB_ENGINE privilege assignment and consider upgrading to a patched version. Additionally, review RBAC configurations to ensure users only have minimum necessary 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
Emc Powerscale OnefsOperating system
Affected:= 8.1.0= 8.1.1= 8.1.2= 8.2.0= 8.2.1= 8.2.2= 9.0.0= 9.1.0

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
High
Availability
High

CVSS:3.1/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 checks

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

  1. Identify PowerScale OneFS version
    Run 'isi version' or check the OneFS web interface under Cluster Management > General > Version to determine the installed OneFS version.
    Affected if The installed version is 8.1.0, 8.1.1, 8.1.2, 8.2.0, 8.2.1, 8.2.2, 9.0.0, or 9.1.0.
  2. Enumerate RBAC privileges assigned to users
    Use the OneFS CLI command 'isi auth' or check the Identity Management section in the web interface to list all users and their assigned RBAC privileges. Look specifically for the ISI_PRIV_JOB_ENGINE privilege.
    Affected if Any user account is assigned the ISI_PRIV_JOB_ENGINE privilege.
  3. Verify PermissionRepair job availability
    Check if the PermissionRepair job is present and can be initiated by running 'isi job jobs list' or accessing Job > Jobs via the OneFS web interface. The job is typically found under the job type 'PermissionRepair'.
    Affected if The PermissionRepair job exists and is accessible to users with ISI_PRIV_JOB_ENGINE privilege.
  4. Audit RBAC role assignments for high-privilege roles
    Review all RBAC role assignments using 'isi auth roles list' or through the OneFS web interface under Access > RBAC > Roles. Identify if any elevated roles (such as Administrator) are present beyond expected administrative accounts.
    Affected if Users with ISI_PRIV_JOB_ENGINE privilege can potentially elevate their privileges beyond their assigned role level through the PermissionRepair job vulnerability.

You are affected if your PowerScale OneFS version is 8.1.0 through 9.1.0 AND any user account possesses the ISI_PRIV_JOB_ENGINE privilege, as that user could exploit the PermissionRepair job to escalate to the highest RBAC privilege level.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict or audit the ISI_PRIV_JOB_ENGINE privilege assignment and consider upgrading to a patched version. Additionally, review RBAC configurations to ensure users only have minimum necessary privileges.

Fix this in Emc Powerscale Onefs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-26191 — 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-26191 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