# CVE-2013-1196: Privilege escalation in n/a

> Local attackers can exploit improper input validation in Cisco network management CLIs to gain root privileges.

- **Severity:** Medium 6.8 (`AV:L/AC:L/Au:S/C:C/I:C/A:C`)
- **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:** 29 Apr 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2x3p-pc2g-c463

## What is CVE-2013-1196?

CVE-2013-1196 is a medium-severity vulnerability in n/a, published on 29 Apr 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The command-line interface in Cisco Secure Access Control System (ACS), Identity Services Engine Software, Context Directory Agent, Application Networking Manager (ANM), Prime Network Control System, Prime LAN Management Solution (LMS), Prime Collaboration, Unified Provisioning Manager, Network Services Manager, Prime Data Center Network Manager (DCNM), and Quad does not properly validate input, which allows local users to obtain root privileges via unspecified vectors, aka Bug IDs CSCug29384, CSCug13866, CSCug29400, CSCug29406, CSCug29411, CSCug29413, CSCug29416, CSCug29418, CSCug29422, CSCug29425, and CSCug29426, a different issue than CVE-2013-1125.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-1196?

It affects 11 products.


Products: Cisco Application Networking Manager, Cisco Context Directory Agent, Cisco Identity Services Engine Software, Cisco Network Services Manager, Cisco Prime Collaboration, Cisco Prime Data Center Network Manager, Cisco Prime Lan Management Solution, Cisco Prime Network Control System, Cisco Quad, Cisco Secure Access Control System, Cisco Unified Provisioning Manager.

## How do I fix CVE-2013-1196?

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

## Is CVE-2013-1196 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0616](https://insights.sbomify.com/CVE-2009-0616/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2009-0617](https://insights.sbomify.com/CVE-2009-0617/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2009-0618](https://insights.sbomify.com/CVE-2009-0618/): Privilege escalation in n/a (high 8.5)
- [CVE-2015-0651](https://insights.sbomify.com/CVE-2015-0651/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-1125](https://insights.sbomify.com/CVE-2013-1125/): Privilege escalation in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1196 and fix it if it is affected.

What it is: CVE-2013-1196 is a medium-severity vulnerability in n/a, published on 29 Apr 2013. 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-2013-1196 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-2013-1196/ (Markdown: https://insights.sbomify.com/CVE-2013-1196/index.md)
```

## Sources

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

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