CVE-2013-5556
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 license-installation module on the Cisco Nexus 1000V switch 4.2(1)SV1(5.2b) and earlier for VMware vSphere, Cisco Nexus 1000V switch 5.2(1)SM1(5.1) for Microsoft Hyper-V, and Cisco Virtual Security Gateway 4.2(1)VSG1(1) for Nexus 1000V switches allows local users to gain privileges and execute arbitrary commands via crafted "install all iso" arguments, aka Bug ID CSCui21340.
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 confidenceThis is a command injection vulnerability in the license-installation module of Cisco Nexus 1000V switch and Cisco Virtual Security Gateway. Local attackers can inject arbitrary commands through crafted 'install all iso' arguments, achieving privilege escalation and executing commands 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= 4.2\(1\)vsg1\(1\)= 5.2\(1\)sm1\(5.1\)<= 4.2\(1\)sv1\(5.2b\)= 4.2\(1\)_sv1\(4\)= 4.2\(1\)_sv1\(4a\)= 4.2\(1\)_sv1\(4b\)= 4.2\(1\)sv1\(5.1\)= 4.2\(1\)sv1\(5.1a\)= 4.2\(1\)sv1\(5.2\)CVSS 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 Cisco productRun 'show version' or check the system prompt to confirm if the device is Cisco Nexus 1000V or Cisco Virtual Security Gateway (VSG).Affected if The device is a Cisco Nexus 1000V switch or Cisco Virtual Security Gateway.
-
Determine the installed versionRun 'show version' and look for the software version number (for Nexus 1000V, typically shown as 4.2(1)SV1(x) or 5.2(1)SM1(x); for VSG, shown as 4.2(1)VSG1(x)). Compare this version to the affected ranges: Nexus 1000V versions 4.2(1)SV1(4), 4.2(1)SV1(4a), 4.2(1)SV1(4b), 4.2(1)SV1(5.1), 4.2(1)SV1(5.1a), 4.2(1)SV1(5.2), and 4.2(1)SV1(5.2b) or earlier; VSG version 4.2(1)VSG1(1); and Hyper-V SM1 version 5.2(1)SM1(5.1).Affected if The installed version matches one of the listed affected versions.
-
Verify license installation module accessAttempt to access the license installation module via 'install all iso' command or check if the feature is exposed via CLI. Review role-based access control (RBAC) configuration using 'show role' and 'show user-account' to determine which local users can access the license installation feature.Affected if Local users with limited privileges can access the license-installation module without proper restrictions.
-
Audit local user accounts and permissionsRun 'show user-account' and 'show role' to list all configured local users and their assigned roles. Check if untrusted or low-privilege local accounts exist that could potentially invoke the 'install all iso' command.Affected if There are local users with permissions to execute license installation commands who should not have such access.
The environment is affected if the device runs Cisco Nexus 1000V or Virtual Security Gateway AND the installed version matches any of the affected versions listed AND local users have access to the license-installation module.
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-supplied patches for the affected versions (4.2(1)SV1(5.2b) and earlier for VMware, 5.2(1)SM1(5.1) for Hyper-V, and 4.2(1)VSG1(1) for VSG). Restrict local administrative access to the license-installation module and audit user permissions.
- 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-5556 — 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-5556 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