# CVE-2019-1889: Cisco Application Policy Infrastructure Controller REST API Privilege Escalation Vulnerability

> An authenticated administrator can escalate privileges to root by uploading malicious software via the REST API due to insufficient file path validation.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jul 2019
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-p5h6-5443-r463

## What is CVE-2019-1889?

CVE-2019-1889 is a high-severity vulnerability in Cisco Application Policy Infrastructure Controller (APIC), published on 4 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the REST API for software device management in Cisco Application Policy Infrastructure Controller (APIC) Software could allow an authenticated, remote attacker to escalate privileges to root on an affected device. The vulnerability is due to incomplete validation and error checking for the file path when specific software is uploaded. An attacker could exploit this vulnerability by uploading malicious software using the REST API. A successful exploit could allow an attacker to escalate their privilege level to root. The attacker would need to have the administrator role on the device.

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

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

It affects 1 product.


Products: Cisco Application Policy Infrastructure Controller.

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

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

## Is CVE-2019-1889 being exploited?

There is no known exploitation of CVE-2019-1889 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-1889 and fix it if it is affected.

What it is: CVE-2019-1889 is a high-severity vulnerability in Cisco Application Policy Infrastructure Controller (APIC), published on 4 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1889 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-1889/ (Markdown: https://insights.sbomify.com/CVE-2019-1889/index.md)
```

## Sources

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

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