# CVE-2018-0252: Denial of service in Cisco Wireless LAN Controller

> Remote unauthenticated attackers can cause Cisco Wireless LAN Controllers to reload by sending malformed IPv4 fragments, resulting in a denial of service.

- **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:** 2 May 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-rfmq-5r75-j8r9

## What is CVE-2018-0252?

CVE-2018-0252 is a high-severity denial of service vulnerability in Cisco Wireless Lan Controller Software, published on 2 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the IP Version 4 (IPv4) fragment reassembly function of Cisco 3500, 5500, and 8500 Series Wireless LAN Controller Software could allow an unauthenticated, remote attacker to cause an affected device to reload unexpectedly, resulting in a denial of service (DoS) condition. The vulnerability is due to a corruption of an internal data structure process that occurs when the affected software reassembles certain IPv4 packets. An attacker could exploit this vulnerability by sending certain malformed IPv4 fragments to an affected device. A successful exploit could allow the attacker to cause the device to reload, resulting in a DoS condition. This vulnerability affects all releases of 8.4 until the first fixed release for the 5500 and 8500 Series Wireless LAN Controllers and releases 8.5.103.0 and 8.5.105.0 for the 3500, 5500, and 8500 Series Wireless LAN Controllers. Cisco Bug IDs: CSCvf89222.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-399

## Which versions are affected by CVE-2018-0252?

It affects 1 product.


Products: Cisco Wireless Lan Controller Software.

## How do I fix CVE-2018-0252?

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

## Is CVE-2018-0252 being exploited?

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

## Other vulnerabilities in Cisco Wireless Lan Controller Software

- [CVE-2007-2036](https://insights.sbomify.com/CVE-2007-2036/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2016-1363](https://insights.sbomify.com/CVE-2016-1363/): Memory corruption in n/a (critical 9.8)
- [CVE-2015-6314](https://insights.sbomify.com/CVE-2015-6314/): Auth bypass in n/a (critical 9.8)
- [CVE-2010-2842](https://insights.sbomify.com/CVE-2010-2842/): Privilege escalation in n/a (critical 9.0)
- [CVE-2010-2843](https://insights.sbomify.com/CVE-2010-2843/): Privilege escalation in n/a (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0252 and fix it if it is affected.

What it is: CVE-2018-0252 is a high-severity denial of service vulnerability in Cisco Wireless Lan Controller Software, published on 2 May 2018. 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-2018-0252 in the wild and no public exploit code.

Affected product: Cisco Wireless Lan Controller 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-2018-0252/ (Markdown: https://insights.sbomify.com/CVE-2018-0252/index.md)
```

## Sources

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

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