# CVE-2019-1586: Cisco Application Policy Infrastructure Controller Recoverable Encryption Key Vulnerability

> An attacker with physical access can retrieve encryption keys from the disk, leading to the disclosure of sensitive information on Cisco APIC devices.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-f958-6c9p-jx25

## What is CVE-2019-1586?

CVE-2019-1586 is a medium-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 Cisco Application Policy Infrastructure Controller (APIC) Software could allow an unauthenticated, local attacker with physical access to obtain sensitive information from an affected device. The vulnerability is due to insecure removal of cleartext encryption keys stored on local partitions in the hard drive of an affected device. An attacker could exploit this vulnerability by retrieving data from the physical disk on the affected partition(s). A successful exploit could allow the attacker to retrieve encryption keys, possibly allowing the attacker to further decrypt other data and sensitive information on the device, which could lead to the disclosure of confidential information.

Weakness: CWE-459 (Incomplete Cleanup), CWE-320

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

It affects 1 product.


Products: Cisco Application Policy Infrastructure Controller.

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

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

## Is CVE-2019-1586 being exploited?

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

What it is: CVE-2019-1586 is a medium-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-1586 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-1586/ (Markdown: https://insights.sbomify.com/CVE-2019-1586/index.md)
```

## Sources

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

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