CVE-2011-1421
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 · uneditedEMC NetWorker 7.5.x before 7.5.4.3 and 7.6.x before 7.6.1.5, when the client push feature is enabled, uses weak permissions for an unspecified file, 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 confidenceEMC NetWorker versions 7.5.x before 7.5.4.3 and 7.6.x before 7.6.1.5 contain a weak file permissions vulnerability when the client push feature is enabled. An unspecified file has insufficient access controls, allowing local unprivileged users to potentially escalate privileges to gain higher system access.
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.5.2.0= 7.5.2.1= 7.5.2.2= 7.5.2.3= 7.5.2.4= 7.5.3= 7.5.3.1= 7.5.3.2= 7.5.3.3= 7.5.3.4= 7.5.3.5= 7.5.4CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/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 versionRun 'nsradmin -p nsmi -c show all' or check the NetWorker installation directory for version information. On Windows, check 'Program Files\Legato\nsr\version' or similar. On Unix/Linux, check '/usr/sbin/nsr/version' or '/opt/nsr/version'.Affected if The installed version is 7.5.x before 7.5.4.3, or 7.6.x before 7.6.1.5, or matches any of these specific versions: 7.5.2.0 through 7.5.4, 7.5.3 through 7.5.3.5, or 7.6.0 through 7.6.1.4
-
Determine if client push feature is enabledCheck NetWorker configuration files or resource settings for the client push feature. This may be found in 'nsrla' or related client access configuration. Consult NetWorker documentation for the specific configuration parameter that controls the client push feature.Affected if The client push feature is enabled in the NetWorker configuration
-
Inspect file permissions in NetWorker directoriesExamine file permissions on the NetWorker installation directory and subdirectories, particularly those related to client push functionality. Use 'ls -la' on Unix/Linux or check Security properties on Windows. Look for files with overly permissive ACLs (e.g., world-writable or readable by unprivileged users).Affected if Any critical file in the NetWorker installation directory has weak permissions (world-readable/writable or accessible by unprivileged users)
-
Verify user access to NetWorker filesIdentify which users and groups have access to NetWorker configuration and binary directories. Check if unprivileged local users have read or write access to sensitive NetWorker files.Affected if Unprivileged local users have access to files that should be restricted to administrator or NetWorker service accounts
You are affected if NetWorker is installed with a version in the 7.5.x before 7.5.4.3 or 7.6.x before 7.6.1.5 range AND the client push feature is enabled, resulting in weak file permissions that unprivileged users could exploit for privilege escalation.
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 7.5.4.3/7.6.1.5 or later to address the weak permissions. If patching is not immediately feasible, evaluate disabling the client push feature if business operations permit, and restrict file system access to the NetWorker directories.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1421 — 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-2011-1421 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