CVE-2013-3270
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 VNX Control Station before 7.1.70.2 and Celerra Control Station before 6.0.70.1 have an incorrect group ownership for unspecified script files, which allows local users to gain privileges by leveraging nasadmin group membership.
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 VNX and Celerra Control Stations ship with script files that have incorrect group ownership, allowing local users who are members of the nasadmin group to modify these scripts and execute them with elevated privileges. This enables local privilege escalation from nasadmin to root.
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.1.70.1<= 6.0.70.0CVSS 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
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:S/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 the product and versionRun 'product: get detail' or check /etc/product_version on the Control Station to determine if it is EMC VNX or Celerra Control Station and note the installed version numberAffected if The product is VNX Control Station with version <= 7.1.70.1 OR Celerra Control Station with version <= 6.0.70.0
-
Verify nasadmin group membershipRun 'id' or 'groups <username>' to check if the current user or target user is a member of the nasadmin groupAffected if The user is a member of the nasadmin group
-
Locate scripts with elevated privilege pathsSearch for script files in directories such as /nas, /opt/Navisphere/bin, or /usr/local/bin that are executed by root or contain references to root-level operations (e.g., grep -r 'root' /nas/*.sh)Affected if Script files intended for privileged execution exist on the system
-
Check group ownership of affected scriptsRun 'ls -la' on the identified script files and verify if they are owned by group 'nasadmin' or have 'nasadmin' as the group ownerAffected if The scripts are owned by the nasadmin group or have nasadmin group write permissions
-
Verify write permissions on scriptsCheck file permissions using 'ls -la <script>' and look for write permission (w) set for the group (e.g., permissions like -rwxrwx---)Affected if The scripts have group write permission for the nasadmin group, allowing modification by nasadmin users
You are affected if the system runs a VNX Control Station <= 7.1.70.1 or Celerra Control Station <= 6.0.70.0, you have nasadmin group access, and scripts intended for root execution are writable by the nasadmin group.
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 dataUpgrade EMC VNX Control Station to version 7.1.70.2 or later, and Celerra Control Station to 6.0.70.1 or later. Alternatively, identify and correct the group ownership of affected script files to restrict write access.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3270 — 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-3270 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