Prime Network Analysis Module SoftwarePlugin / extension · Cisco
CVE-2016-1390
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 · uneditedCisco Prime Network Analysis Module (NAM) before 6.1(1) patch.6.1-2-final and 6.2.x before 6.2(1) and Prime Virtual Network Analysis Module (vNAM) before 6.1(1) patch.6.1-2-final and 6.2.x before 6.2(1) allow local users to obtain root access via crafted CLI input, aka Bug ID CSCuy21892.
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 local privilege escalation vulnerability in Cisco Prime Network Analysis Module (NAM) and Virtual NAM (vNAM). The flaw exists in the CLI interface where insufficient input validation allows authenticated local users to inject crafted commands and gain root-level access to the underlying operating system.
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
Prime Network Analysis Module SoftwarePlugin / extension
= 5.0.0= 5.0.1= 5.0.2= 5.1.0= 5.1.2= 6.0.2= 6.1.0= 6.1.1= 6.2.0
Prime Virtual Network Analysis Module SoftwarePlugin / extension
= 6.0.0= 6.1.0= 6.2.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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed product and versionAccess the CLI interface and run 'show version' or check the web administration interface under Help > About to determine if you are running Cisco Prime Network Analysis Module (NAM) or Virtual NAM (vNAM) and note the exact software version number.Affected if The installed version matches any of the following: NAM versions 5.0.0, 5.0.1, 5.0.2, 5.1.0, 5.1.2, 6.0.2, 6.1.0, 6.1.1, 6.2.0 or vNAM versions 6.0.0, 6.1.0, 6.2.0.
-
Verify CLI access is availableConfirm that the CLI interface is accessible and that local authenticated user accounts exist on the system. Use 'show users' or similar command to list active CLI sessions.Affected if Local authenticated CLI access is available, which is required for the privilege escalation exploit to be executable.
-
Check for unexpected root-level commandsReview CLI command history or audit logs for any commands that appear to attempt command injection (such as commands containing shell metacharacters or unusual privilege escalation attempts). Look for commands that deviate from standard NAM administrative operations.Affected if Evidence of command injection attempts or unauthorized root-level access is present in logs or system state.
You are affected if you are running any of the listed affected versions (5.0.0-6.2.0 range for NAM or 6.0.0-6.2.0 for vNAM) and the CLI interface is accessible to local authenticated users.
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 the vendor-supplied software update: upgrade to version 6.1(1) patch 6.1-2-final or 6.2(1) or later for both NAM and vNAM products.
Fix this in Prime Network Analysis Module Software
Scoped from the published advisory
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1390 — 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-2016-1390 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