# CVE-2019-1890: Cisco Nexus 9000 Series Fabric Switches ACI Mode Fabric Infrastructure VLAN Unauthorized Access Vulnerability

> An adjacent attacker can bypass LLDP security checks to connect an unauthorized server to the privileged infrastructure VLAN, gaining access to APIC services.

- **Severity:** High 7.4 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/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:** 4 Jul 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-6gv5-cvcq-3x2c

## What is CVE-2019-1890?

CVE-2019-1890 is a high-severity authentication bypass vulnerability in Cisco NX-OS System Software in ACI Mode 11.0.1b, published on 4 Jul 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 fabric infrastructure VLAN connection establishment of the Cisco Nexus 9000 Series Application Centric Infrastructure (ACI) Mode Switch Software could allow an unauthenticated, adjacent attacker to bypass security validations and connect an unauthorized server to the infrastructure VLAN. The vulnerability is due to insufficient security requirements during the Link Layer Discovery Protocol (LLDP) setup phase of the infrastructure VLAN. An attacker could exploit this vulnerability by sending a malicious LLDP packet on the adjacent subnet to the Cisco Nexus 9000 Series Switch in ACI mode. A successful exploit could allow the attacker to connect an unauthorized server to the infrastructure VLAN, which is highly privileged. With a connection to the infrastructure VLAN, the attacker can make unauthorized connections to Cisco Application Policy Infrastructure Controller (APIC) services or join other host endpoints.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Cisco Application Policy Infrastructure Controller.

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

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

## Is CVE-2019-1890 being exploited?

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

## Other vulnerabilities in Cisco NX-OS System Software in ACI Mode 11.0.1b

- [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-1890 and fix it if it is affected.

What it is: CVE-2019-1890 is a high-severity authentication bypass vulnerability in Cisco NX-OS System Software in ACI Mode 11.0.1b, published on 4 Jul 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-1890 in the wild and no public exploit code.

Affected product: Cisco NX-OS System Software in ACI Mode 11.0.1b. 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-1890/ (Markdown: https://insights.sbomify.com/CVE-2019-1890/index.md)
```

## Sources

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

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