CVE-2013-0940
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 · uneditedThe nsrpush process in the client in EMC NetWorker before 7.6.5.3 and 8.x before 8.0.1.4 sets weak permissions for unspecified files, which allows local users to gain privileges via unknown vectors.
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 nsrpush process in EMC NetWorker client versions before 7.6.5.3 and 8.x before 8.0.1.4 sets weak (likely world-writable or overly permissive) file permissions on unspecified files. This local privilege escalation vulnerability allows unprivileged local users to potentially modify or replace files with elevated 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<= 7.6.5.2= 6.0= 6.1= 7.0= 7.2= 7.3= 7.3.2= 7.4= 7.4.5.4= 7.4.5.5= 7.4.5.6= 7.4.5.10CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 installation and versionLocate the NetWorker installation directory (common paths: /opt/networker, /usr/nsr, C:\Program Files\EMC NetWorker) and check the version file or binary version (nsrpexec -V, nsrinfo -V, or check version in registry on Windows)Affected if Version is 7.6.5.2 or earlier, or 8.x before 8.0.1.4 (including 6.0, 6.1, 7.0, 7.2, 7.3, 7.3.2, 7.4, 7.4.5.4, 7.4.5.5, 7.4.5.6, 7.4.5.10)
-
Locate the nsrpush binary and processFind the nsrpush executable in the NetWorker bin directory (commonly /opt/networker/bin/nsrpush or C:\Program Files\EMC NetWorker\bin\nsrpush.exe) and verify the process exists or has been runAffected if The nsrpush binary is present in a version that is vulnerable per the version check above
-
Audit file permissions in NetWorker directoriesUse filesystem inspection commands: on Unix/Linux run 'ls -la' or 'find /opt/networker -perm -002' to find world-writable files; on Windows use icacls or accesschk to identify overly permissive ACLsAffected if Any critical NetWorker files (especially in bin, lib, or config directories) are world-writable or group-writable allowing modification by unprivileged users
-
Verify unprivileged user write accessAttempt to create or modify files in NetWorker directories using a low-privilege test account or use tools like 'find /opt/networker -perm -002 -type f' to list all world-writable filesAffected if Non-admin users can write to files that the nsrpush process would execute or that reside in protected NetWorker directories
If NetWorker version is 7.6.5.2 or earlier, or 8.x before 8.0.1.4, AND the nsrpush binary exists with weak file permissions allowing unprivileged modification, the environment is affected by CVE-2013-0940.
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 patches (NetWorker 7.6.5.3 or 8.0.1.4 and later). Until patched, audit file permissions on the NetWorker installation directory and restrict write access to only privileged users.
- 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-2013-0940 — 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-2013-0940 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