# CVE-2016-1390: Privilege escalation in n/a

> Local attackers can gain root access on Cisco Prime NAM devices by submitting crafted CLI input, requiring immediate patching.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vcpr-g527-vqvc

## What is CVE-2016-1390?

CVE-2016-1390 is a high-severity vulnerability in n/a, published on 4 Jun 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cisco 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-1390?

It affects 2 products.


Products: Cisco Prime Network Analysis Module Software, Cisco Prime Virtual Network Analysis Module Software.

## How do I fix CVE-2016-1390?

No fix has been published for CVE-2016-1390 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-1390 being exploited?

There is no known exploitation of CVE-2016-1390 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2016-1391](https://insights.sbomify.com/CVE-2016-1391/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1390 and fix it if it is affected.

What it is: CVE-2016-1390 is a high-severity vulnerability in n/a, published on 4 Jun 2016. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1390 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-1390/ (Markdown: https://insights.sbomify.com/CVE-2016-1390/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-1390
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-1390
- OSV: https://osv.dev/vulnerability/CVE-2016-1390

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-1390/
Summaries are generated and may contain mistakes; the official description above is the record.