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

> Remote authenticated attackers can execute arbitrary commands on Cisco UCS Performance Manager via crafted GET request parameters.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2j5h-jch9-hqpj

## What is CVE-2016-1374?

CVE-2016-1374 is a high-severity command injection vulnerability in n/a, published on 28 Jul 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web framework in Cisco Unified Computing System (UCS) Performance Manager 2.0.0 and earlier allows remote authenticated users to execute arbitrary commands via crafted parameters in a GET request, aka Bug ID CSCuy07827.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Cisco Unified Computing System Performance Manager.

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

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

## Is CVE-2016-1374 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-1374 is a high-severity command injection vulnerability in n/a, published on 28 Jul 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1374 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-1374/ (Markdown: https://insights.sbomify.com/CVE-2016-1374/index.md)
```

## Sources

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

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