CVE-2019-1597

Cisco FXOS and NX-OS Lightweight Directory Access Protocol Denial of Service Vulnerabilities

HIGH
8.6
CVSS Score
Published: March 7, 2019 at 07:00 PM UTC
Updated: June 17, 2026 at 02:28 AM UTC
16 products affected across 1 vendorNx OSFirepower Extensible Operating SystemFirepower 9300

Using Firepower 4100 Series Next-Generation Firewalls by Cisco?

Get instant alerts when new vulnerabilities affect Firepower 4100 Series Next-Generation Firewalls - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.6
Exploit prediction
EPSS 3%
SSVC
No known exploit

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).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.0.1.2012.0.1.201 < v < 2.2.2.542.2.2.54 < v < 2.3.1.75
Affected range stops below 2.0.1.201, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.2.2.54, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.3.1.75, so it looks safe — our inference, not a vendor statement
cisco-firepower-4100 (environment) · cisco-firepower-9300 (environment)
v < 3.2(2b)v < 6.2(20)v < 7.0(3)i7(1)v < 7.0(3)i7(2)v < 8.2(1)6.2(20) < v < 7.3(2)d1(1)7.3(2)d1(1) < v < 8.2(1)
Affected range stops below 3.2(2b), so it looks safe — our inference, not a vendor statement
Affected range stops below 6.2(20), so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0(3)i7(1), so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0(3)i7(2), so it looks safe — our inference, not a vendor statement
Affected range stops below 7.3(2)d1(1), so it looks safe — our inference, not a vendor statement
Affected range stops below 8.2(1), so it looks safe — our inference, not a vendor statement
cisco-mds-9000 (environment) · cisco-nexus-3000 (environment) · cisco-nexus-3500 (environment) · cisco-nexus-7000 (environment) · cisco-nexus-7700 (environment) · cisco-nexus-9000 (environment) · cisco-ucs-6200 (environment) · cisco-ucs-6300 (environment)
v < 2.0.1.201v < 2.2.2.54v < 2.3.1.75
Affected range stops below 2.0.1.201, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.2.2.54, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.3.1.75, so it looks safe — our inference, not a vendor statement
v < 2.0.1.201v < 2.2.2.54v < 2.3.1.75
Affected range stops below 2.0.1.201, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.2.2.54, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.3.1.75, so it looks safe — our inference, not a vendor statement
v < 8.2(1)
Affected range stops below 8.2(1), so it looks safe — our inference, not a vendor statement
v < 7.0(3)I7(1)
Affected range stops below 7.0(3)I7(1), so it looks safe — our inference, not a vendor statement
v < 7.0(3)I7(2)
Affected range stops below 7.0(3)I7(2), so it looks safe — our inference, not a vendor statement
v < 8.2(1)
Affected range stops below 8.2(1), so it looks safe — our inference, not a vendor statement
v < 8.2(1)
Affected range stops below 8.2(1), so it looks safe — our inference, not a vendor statement
v < 7.0(3)I7(1)
Affected range stops below 7.0(3)I7(1), so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.6HIGHcisco
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card