# CVE-2017-12274: Denial of service in Cisco Aironet 1560, 2800, and 3800 Series Access Point Platforms

> An unauthenticated adjacent attacker can cause a denial of service on Cisco Aironet Access Points by sending malformed EAP frames, requiring manual power cycling to recover.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/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:** 2 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2mvg-4w6c-5r8v

## What is CVE-2017-12274?

CVE-2017-12274 is a medium-severity denial of service vulnerability in Cisco Aironet 1560, 2800, and 3800 Series Access Point Platforms, published on 2 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in Extensible Authentication Protocol (EAP) ingress frame processing for the Cisco Aironet 1560, 2800, and 3800 Series Access Points could allow an unauthenticated, Layer 2 radio frequency (RF) adjacent attacker to cause the Access Point (AP) to reload, resulting in a denial of service (DoS) condition. The vulnerability is due to insufficient validation of the EAP frame. An attacker could exploit this vulnerability by sending a malformed EAP frame to the targeted device. A successful exploit could allow the attacker to cause the AP to reload, resulting in a DoS condition while the AP is reloading. It may be necessary to manually power cycle the device in order for it to recover. This vulnerability affects the following Cisco products running either the Lightweight AP Software or Mobility Express image: Aironet 1560 Series Access Points, Aironet 2800 Series Access Points, Aironet 3800 Series Access Points. Note: The Cisco Aironet 1560 Series Access Point device is supported as of release 8.3.112.0. Cisco Bug IDs: CSCve18935.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-12274?

It affects 3 products.


Products: Cisco Aironet 1562 Firmware, Cisco Aironet 2800 Firmware, Cisco Aironet 3800 Firmware.

## How do I fix CVE-2017-12274?

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

## Is CVE-2017-12274 being exploited?

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

## Other vulnerabilities in Cisco Aironet 1560, 2800, and 3800 Series Access Point Platforms

- [CVE-2017-12273](https://insights.sbomify.com/CVE-2017-12273/): A vulnerability in 802.11 association request frame processing for the Cisco Aironet 1560, 2800, and 3800 Series Access Points could allow a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12274 and fix it if it is affected.

What it is: CVE-2017-12274 is a medium-severity denial of service vulnerability in Cisco Aironet 1560, 2800, and 3800 Series Access Point Platforms, published on 2 Nov 2017. 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-2017-12274 in the wild and no public exploit code.

Affected product: Cisco Aironet 1560, 2800, and 3800 Series Access Point Platforms. 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-2017-12274/ (Markdown: https://insights.sbomify.com/CVE-2017-12274/index.md)
```

## Sources

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

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