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

> Local attackers can gain root access on Cisco APIC devices due to mishandled binary files in the installation component.

- **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:** 10 Jun 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qmwv-v38g-gxjq

## What is CVE-2016-1420?

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

### Official description

The installation component on Cisco Application Policy Infrastructure Controller (APIC) devices with software before 1.3(2f) mishandles binary files, which allows local users to obtain root access via unspecified vectors, aka Bug ID CSCuz72347.

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

It affects 2 products.


Products: Cisco Application Infrastructure Controller, Cisco Application Policy Infrastructure Controller Firmware.

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

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

## Is CVE-2016-1420 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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