# CVE-2019-1682: Cisco Application Policy Infrastructure Controller Privilege Escalation Vulnerability

> An authenticated local attacker can escalate privileges to root on Cisco APIC devices by exploiting insufficient input validation in the FUSE filesystem.

- **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:** 3 May 2019
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-w5xg-prmx-v5rm

## What is CVE-2019-1682?

CVE-2019-1682 is a high-severity vulnerability in Cisco Application Policy Infrastructure Controller (APIC), published on 3 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the FUSE filesystem functionality for Cisco Application Policy Infrastructure Controller (APIC) software could allow an authenticated, local attacker to escalate privileges to root on an affected device. The vulnerability is due to insufficient input validation for certain command strings issued on the CLI of the affected device. An attacker with write permissions for files within a readable folder on the device could alter certain definitions in the affected file. A successful exploit could allow an attacker to cause the underlying FUSE driver to execute said crafted commands, elevating the attacker's privileges to root on an affected device.

Weakness: CWE-20 (Improper Input Validation), CWE-264

## Which versions are affected by CVE-2019-1682?

It affects 1 product.


Products: Cisco Application Policy Infrastructure Controller.

## How do I fix CVE-2019-1682?

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

## Is CVE-2019-1682 being exploited?

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

## Other vulnerabilities in Cisco Application Policy Infrastructure Controller (APIC)

- [CVE-2021-1393](https://insights.sbomify.com/CVE-2021-1393/): Cisco Application Services Engine Unauthorized Access Vulnerabilities (critical 9.8)
- [CVE-2021-1396](https://insights.sbomify.com/CVE-2021-1396/): Cisco Application Services Engine Unauthorized Access Vulnerabilities (critical 9.8)
- [CVE-2021-1577](https://insights.sbomify.com/CVE-2021-1577/): Cisco Application Policy Infrastructure Controller Arbitrary File Read and Write Vulnerability (critical 9.1)
- [CVE-2023-20011](https://insights.sbomify.com/CVE-2023-20011/): Cross-site request forgery in Cisco Application Policy Infrastructure Controller (APIC) (high 8.8)
- [CVE-2021-1578](https://insights.sbomify.com/CVE-2021-1578/): Cisco Application Policy Infrastructure Controller Privilege Escalation Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1682 and fix it if it is affected.

What it is: CVE-2019-1682 is a high-severity vulnerability in Cisco Application Policy Infrastructure Controller (APIC), published on 3 May 2019. 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-2019-1682 in the wild and no public exploit code.

Affected product: Cisco Application Policy Infrastructure Controller (APIC). 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-2019-1682/ (Markdown: https://insights.sbomify.com/CVE-2019-1682/index.md)
```

## Sources

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

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