CVE-2020-26182
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 NetWorker versions prior to 19.3.0.2 contain an incorrect privilege assignment vulnerability. A non-LDAP remote user with low privileges may exploit this vulnerability to perform 'saveset' related operations in an unintended manner. The vulnerability is not exploitable by users authenticated via LDAP.
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 confidenceDell EMC NetWorker versions prior to 19.3.0.2 have an incorrect privilege assignment vulnerability where non-LDAP remote users with low privileges can perform saveset-related operations they should not have access to. This is an authorization bypass affecting only non-LDAP authenticated users.
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< 19.3.0.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 NetWorker versionRun 'nsrversion -v' or check the About section in the NetWorker Administration GUI to retrieve the installed version numberAffected if The installed version is lower than 19.3.0.2 (e.g., 19.2.x, 19.1.x, 18.x, earlier)
-
Confirm non-LDAP authentication is in useCheck the NetWorker authentication configuration in the Administration GUI under 'Users and Groups' or inspect the nsrauthd configuration to determine if local or non-LDAP remote users are enabledAffected if Non-LDAP local or remote user accounts are configured and permitted to authenticate to NetWorker
-
Review saveset operation permissionsExamine user permissions for saveset-related operations (save, recover, migrate, clone) using 'nsradmin -s <server> -c "show rights"' or through the GUI user permission settingsAffected if Low-privilege non-LDAP users have permissions to perform saveset operations they should not have access to
-
Audit recent saveset operationsReview NetWorker audit logs or run 'mminfo -a' to list recent saveset activity and identify any operations performed by low-privilege non-LDAP usersAffected if Low-privilege non-LDAP users have performed saveset-related operations they should not be authorized to perform
A user is affected if their NetWorker installation is version 19.3.0.2 or earlier AND non-LDAP authenticated users exist in the environment who could potentially perform unauthorized saveset operations.
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 data19.3.0.2
Upgrade Dell EMC NetWorker to version 19.3.0.2 or later to remediate this vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26182 — 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-26182 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