# CVE-2019-1692: Information disclosure in Cisco Application Policy Infrastructure Controller (APIC)

> Unauthenticated remote attackers can access sensitive system usage information and tracking data from Cisco APIC devices.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2019
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-q7p6-jrrp-5975

## What is CVE-2019-1692?

CVE-2019-1692 is a medium-severity vulnerability in Cisco Application Policy Infrastructure Controller (APIC), published on 3 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Application Policy Infrastructure Controller (APIC) Software could allow an unauthenticated, remote attacker to access sensitive system usage information. The vulnerability is due to a lack of proper data protection mechanisms for certain components in the underlying Application Centric Infrastructure (ACI). An attacker could exploit this vulnerability by attempting to observe certain network traffic when accessing the APIC. A successful exploit could allow the attacker to access and collect certain tracking data and usage statistics on an affected device.

Weakness: CWE-311 (Missing Encryption of Sensitive Data), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Cisco Application Policy Infrastructure Controller.

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

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

## Is CVE-2019-1692 being exploited?

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

What it is: CVE-2019-1692 is a medium-severity vulnerability in Cisco Application Policy Infrastructure Controller (APIC), published on 3 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1692 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-1692/ (Markdown: https://insights.sbomify.com/CVE-2019-1692/index.md)
```

## Sources

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

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