# CVE-2019-1834: Cisco Aironet Series Access Points Denial of Service Vulnerability

> An adjacent attacker can cause a denial of service on Cisco Aironet Access Points by sending crafted wireless packets when port security is enabled on the connected switch.

- **Severity:** High 7.4 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-mvvv-8xrh-cv67

## What is CVE-2019-1834?

CVE-2019-1834 is a high-severity denial of service vulnerability in Cisco Aironet Access Point Software, published on 18 Apr 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 internal packet processing of Cisco Aironet Series Access Points (APs) could allow an unauthenticated, adjacent attacker to cause a denial of service (DoS) condition on an affected AP if the switch interface where the AP is connected has port security configured. The vulnerability exists because the AP forwards some malformed wireless client packets outside of the Control and Provisioning of Wireless Access Points (CAPWAP) tunnel. An attacker could exploit this vulnerability by sending crafted wireless packets to an affected AP. A successful exploit could allow the attacker to trigger a security violation on the adjacent switch port, which could result in a DoS condition. Note: Though the Common Vulnerability Scoring System (CVSS) score corresponds to a High Security Impact Rating (SIR), this vulnerability is considered Medium because a workaround is available and exploitation requires a specific switch configuration. There are workarounds that address this vulnerability.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Cisco Aironet Access Point Firmware.

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

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

## Is CVE-2019-1834 being exploited?

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

## Other vulnerabilities in Cisco Aironet Access Point Software

- [CVE-2017-3834](https://insights.sbomify.com/CVE-2017-3834/): Hardcoded credentials in Cisco Aironet 1830 Series and 1850 Series Access Points (critical 9.8)
- [CVE-2017-3873](https://insights.sbomify.com/CVE-2017-3873/): Code injection in Cisco Aironet 1800, 2800, and 3800 Series Access Points (high 7.5)
- [CVE-2019-1826](https://insights.sbomify.com/CVE-2019-1826/): Cisco Aironet Series Access Points Quality of Service Denial of Service Vulnerability (medium 6.8)
- [CVE-2019-1829](https://insights.sbomify.com/CVE-2019-1829/): Cisco Aironet Series Access Points Command Injection Vulnerability (medium 6.7)
- [CVE-2019-1835](https://insights.sbomify.com/CVE-2019-1835/): Cisco Aironet Series Access Points Directory Traversal Vulnerability (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1834 is a high-severity denial of service vulnerability in Cisco Aironet Access Point Software, published on 18 Apr 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-1834 in the wild and no public exploit code.

Affected product: Cisco Aironet Access Point Software. 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-1834/ (Markdown: https://insights.sbomify.com/CVE-2019-1834/index.md)
```

## Sources

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

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