# CVE-2019-1806: Cisco Small Business Series Switches Simple Network Management Protocol Denial of Service Vulnerability

> An authenticated remote attacker can cause a denial of service on Cisco Small Business switches by sending malicious SNMP packets, requiring firmware updates to fix.

- **Severity:** High 7.7 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-cp5x-9q38-h2hj

## What is CVE-2019-1806?

CVE-2019-1806 is a high-severity denial of service vulnerability in Cisco 550X Series Stackable Managed Switches, published on 15 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the Simple Network Management Protocol (SNMP) input packet processor of Cisco Small Business Sx200, Sx300, Sx500, ESW2 Series Managed Switches and Small Business Sx250, Sx350, Sx550 Series Switches could allow an authenticated, remote attacker to cause the SNMP application of an affected device to cease processing traffic, resulting in the CPU utilization reaching one hundred percent. Manual intervention may be required before a device resumes normal operations. The vulnerability is due to improper validation of SNMP protocol data units (PDUs) in SNMP packets. An attacker could exploit this vulnerability by sending a malicious SNMP packet to an affected device. A successful exploit could allow the attacker to cause the device to cease forwarding traffic, which could result in a denial of service (DoS) condition. Cisco has released firmware updates that address this vulnerability.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-20 (Improper Input Validation)

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

It affects 105 products.


Products: Cisco Esw2-350g52dc Firmware, Cisco Esw2-550x48dc Firmware, Cisco Sf200-24 Firmware, Cisco Sf200-24p Firmware, Cisco Sf200-48 Firmware, Cisco Sf200-48p Firmware, Cisco Sf250-24 Firmware, Cisco Sf250-24p Firmware, Cisco Sf250-48 Firmware, Cisco Sf250-48hp Firmware, Cisco Sf300-08 Firmware, Cisco Sf300-24 Firmware, Cisco Sf300-24mp Firmware, Cisco Sf300-24p Firmware, Cisco Sf300-24pp Firmware, Cisco Sf300-48 Firmware, Cisco Sf300-48p Firmware, Cisco Sf300-48pp Firmware, Cisco Sf302-08 Firmware, Cisco Sf302-08mp Firmware and 85 more.

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

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

## Is CVE-2019-1806 being exploited?

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

## Other vulnerabilities in Cisco 550X Series Stackable Managed Switches

- [CVE-2019-1891](https://insights.sbomify.com/CVE-2019-1891/): Cisco Small Business Series Switches HTTP Denial of Service Vulnerability (high 7.5)
- [CVE-2019-1892](https://insights.sbomify.com/CVE-2019-1892/): Cisco Small Business Series Switches Memory Corruption Vulnerability (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1806 is a high-severity denial of service vulnerability in Cisco 550X Series Stackable Managed Switches, published on 15 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1806 in the wild and no public exploit code.

Affected product: Cisco 550X Series Stackable Managed Switches. 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-1806/ (Markdown: https://insights.sbomify.com/CVE-2019-1806/index.md)
```

## Sources

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

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