# CVE-2016-1388: Command injection in n/a

> Remote attackers can execute arbitrary OS commands on Cisco Prime NAM devices via crafted HTTP requests, requiring immediate patching.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6r2x-9rmj-px47

## What is CVE-2016-1388?

CVE-2016-1388 is a critical command injection vulnerability in n/a, published on 3 Jun 2016. An attacker can exploit it over the internet without logging in, 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 remote attackers to execute arbitrary OS commands via a crafted HTTP request, aka Bug ID CSCuy21882.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 3 products.


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

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

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

## Is CVE-2016-1388 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-1388 is a critical command injection vulnerability in n/a, published on 3 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1388 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-1388/ (Markdown: https://insights.sbomify.com/CVE-2016-1388/index.md)
```

## Sources

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

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