# CVE-2019-1597: Cisco FXOS and NX-OS Lightweight Directory Access Protocol Denial of Service Vulnerabilities

> Remote attackers can cause device reloads via crafted LDAP packets, requiring configured LDAP servers, affecting Cisco network infrastructure.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2019
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-c864-jx3f-89v5

## What is CVE-2019-1597?

CVE-2019-1597 is a high-severity denial of service vulnerability in Cisco Firepower Extensible Operating System, published on 7 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple vulnerabilities in the implementation of the Lightweight Directory Access Protocol (LDAP) feature in Cisco FXOS Software and Cisco NX-OS Software could allow an unauthenticated, remote attacker to cause an affected device to reload, resulting in a denial of service (DoS) condition. The vulnerabilities are due to the improper parsing of LDAP packets by an affected device. An attacker could exploit these vulnerabilities by sending an LDAP packet crafted using Basic Encoding Rules (BER) to an affected device. The LDAP packet must have a source IP address of an LDAP server configured on the targeted device. A successful exploit could cause the affected device to reload, resulting in a DoS condition. Firepower 4100 Series Next-Generation Firewalls are affected in versions prior to 2.0.1.201, 2.2.2.54, and 2.3.1.75. Firepower 9300 Security Appliances are affected in versions prior to 2.0.1.201, 2.2.2.54 and 2.3.1.75. MDS 9000 Series Multilayer Switches are affected in versions prior to 8.2(1). Nexus 3000 Series Switches are affected in versions prior to 7.0(3)I7(1). Nexus 3500 Platform Switches are affected in versions prior to 7.0(3)I7(2). Nexus 7000 and 7700 Series Switches are affected in versions prior to 8.2(1). Nexus 9000 Series Switches in Standalone NX-OS Mode are affected in versions prior to 7.0(3)I7(1). Cisco UCS 6200 and 6300 Fabric Interconnect devices are affected in versions prior to 3.2(2b).

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Cisco Firepower Extensible Operating System, Cisco Nx-Os.

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

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

## Is CVE-2019-1597 being exploited?

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

## Other vulnerabilities in Cisco Firepower Extensible Operating System

- [CVE-2018-0310](https://insights.sbomify.com/CVE-2018-0310/): Information disclosure in Cisco FXOS and NX-OS unknown (critical 9.8)
- [CVE-2015-6435](https://insights.sbomify.com/CVE-2015-6435/): Command injection in n/a (critical 9.8)
- [CVE-2021-1368](https://insights.sbomify.com/CVE-2021-1368/): Memory corruption in Cisco NX-OS Software (high 8.8)
- [CVE-2020-3456](https://insights.sbomify.com/CVE-2020-3456/): Cisco FXOS Software Firepower Chassis Manager Cross-Site Request Forgery Vulnerability (high 8.8)
- [CVE-2020-3172](https://insights.sbomify.com/CVE-2020-3172/): Cisco FXOS and NX-OS Software Cisco Discovery Protocol Arbitrary Code Execution and Denial of Service Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1597 is a high-severity denial of service vulnerability in Cisco Firepower Extensible Operating System, published on 7 Mar 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-1597 in the wild and no public exploit code.

Affected product: Cisco Firepower Extensible Operating System. 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-1597/ (Markdown: https://insights.sbomify.com/CVE-2019-1597/index.md)
```

## Sources

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

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