CVE-2020-26183
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 improper authorization vulnerability. Certain remote users with low privileges may exploit this vulnerability to perform 'nsrmmdbd' operations in an unintended manner.
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 before 19.3.0.2 have an improper authorization flaw that allows low-privileged remote users to perform nsrmmdbd (NetWorker media database daemon) operations outside their intended permissions, potentially enabling unauthorized data management or configuration changes.
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 installed package version using the system package manager (e.g., 'rpm -q libnsr' or 'dpkg -l | grep networker')Affected if The installed version is lower than 19.3.0.2 (e.g., 19.1.x, 19.2.x, or earlier)
-
Verify nsrmmdbd service statusCheck if the nsrmmdbd (NetWorker media database daemon) process is running using 'ps -ef | grep nsrmmdbd' or by querying the service status via 'nsradmin -s localhost -i -' followed by 'show service:nsrmmdbd'Affected if The nsrmmdbd daemon is active and accepting remote connections
-
Review remote user access configurationExamine the NetWorker authentication configuration by running 'nsradmin -s localhost -i -' and querying 'select user;show name;show type;show permission' to list users and their assigned permissions, especially for low-privileged accountsAffected if Low-privileged remote users exist with permissions to access nsrmmdbd operations beyond their intended scope
-
Check network exposure of nsrmmdbdReview firewall rules or NetWorker network settings to determine if port 7931 (default nsrmmdbd port) or the configured nsrmmdbd port is exposed to untrusted networks, using 'netstat -an | grep 7931' or equivalentAffected if The nsrmmdbd port is accessible from networks other than trusted administration subnets
You are affected if NetWorker version is below 19.3.0.2 AND the nsrmmdbd daemon is running with low-privileged remote user accounts configured.
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 NetWorker to version 19.3.0.2 or later to obtain the vendor patch addressing the authorization bypass. Review user privilege assignments post-upgrade to ensure least-privilege principles are enforced.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26183 — 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-26183 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