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

> Authenticated users can bypass RBAC restrictions to execute arbitrary CLI commands with admin privileges on Cisco ACE devices.

- **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:** 26 Feb 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4x6r-cv3m-8ffm

## What is CVE-2016-1297?

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

### Official description

The Device Manager GUI in Cisco Application Control Engine (ACE) 4710 A5 before A5(3.1) allows remote authenticated users to bypass intended RBAC restrictions and execute arbitrary CLI commands with admin privileges via an unspecified parameter in a POST request, aka Bug ID CSCul84801.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Cisco Application Control Engine Software.

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

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

## Is CVE-2016-1297 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-3063](https://insights.sbomify.com/CVE-2012-3063/): Missing authorization in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-1297 is a high-severity command injection vulnerability in n/a, published on 26 Feb 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-1297 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-1297/ (Markdown: https://insights.sbomify.com/CVE-2016-1297/index.md)
```

## Sources

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

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