# CVE-2019-1700: Denial of service in Cisco Firepower Extensible Operating System (FXOS)

> An adjacent attacker can cause a denial of service on Cisco Firepower 9000 network modules by sending crafted packets, requiring manual intervention to recover.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **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:** 21 Feb 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-458g-fg5w-22xq

## What is CVE-2019-1700?

CVE-2019-1700 is a medium-severity denial of service vulnerability in Cisco Firepower Extensible Operating System (FXOS), published on 21 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in field-programmable gate array (FPGA) ingress buffer management for the Cisco Firepower 9000 Series with the Cisco Firepower 2-port 100G double-width network module (PID: FPR9K-DNM-2X100G) could allow an unauthenticated, adjacent attacker to cause a denial of service (DoS) condition. Manual intervention may be required before a device will resume normal operations. The vulnerability is due to a logic error in the FPGA related to the processing of different types of input packets. An attacker could exploit this vulnerability by being on the adjacent subnet and sending a crafted sequence of input packets to a specific interface on an affected device. A successful exploit could allow the attacker to cause a queue wedge condition on the interface. When a wedge occurs, the affected device will stop processing any additional packets that are received on the wedged interface. Version 2.2 is affected.

Weakness: CWE-399

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

It affects 1 product.


Products: Cisco Firepower 9000 Firmware.

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

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

## Is CVE-2019-1700 being exploited?

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

## Other vulnerabilities in Cisco Firepower Extensible Operating System (FXOS)

- [CVE-2018-0304](https://insights.sbomify.com/CVE-2018-0304/): Memory corruption in Cisco FXOS and NX-OS unknown (critical 9.8)
- [CVE-2018-0308](https://insights.sbomify.com/CVE-2018-0308/): Memory corruption in Cisco FXOS and NX-OS unknown (critical 9.8)
- [CVE-2018-0312](https://insights.sbomify.com/CVE-2018-0312/): Memory corruption in Cisco FXOS and NX-OS unknown (critical 9.8)
- [CVE-2018-0314](https://insights.sbomify.com/CVE-2018-0314/): Memory corruption in Cisco FXOS and NX-OS unknown (critical 9.8)
- [CVE-2018-0305](https://insights.sbomify.com/CVE-2018-0305/): Null dereference in Cisco FXOS and NX-OS unknown (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1700 is a medium-severity denial of service vulnerability in Cisco Firepower Extensible Operating System (FXOS), published on 21 Feb 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-1700 in the wild and no public exploit code.

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

## Sources

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

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