# CVE-2018-0250: Security feature bypass in Cisco Aironet Access Points

> An authenticated adjacent attacker can bypass FlexConnect ACLs on Cisco Aironet Access Points using Central Web Authentication.

- **Severity:** Medium 4.1 (`CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-wq5x-gxqv-3rgf

## What is CVE-2018-0250?

CVE-2018-0250 is a medium-severity vulnerability in Cisco Aironet Access Points, published on 2 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in Central Web Authentication (CWA) with FlexConnect Access Points (APs) for Cisco Aironet 1560, 1810, 1810w, 1815, 1830, 1850, 2800, and 3800 Series APs could allow an authenticated, adjacent attacker to bypass a configured FlexConnect access control list (ACL). The vulnerability is due to the AP ignoring the ACL download from the client during authentication. An attacker could exploit this vulnerability by connecting to the targeted device with a vulnerable configuration. A successful exploit could allow the attacker to bypass a configured client FlexConnect ACL. This vulnerability affects the following Cisco products if they are running a vulnerable release of Central Web Authentication with FlexConnect Access Points Software: Aironet 1560 Series Access Points, Aironet 1810 Series OfficeExtend Access Points, Aironet 1810w Series Access Points, Aironet 1815 Series Access Points, Aironet 1830 Series Access Points, Aironet 1850 Series Access Points, Aironet 2800 Series Access Points, Aironet 3800 Series Access Points. Note: Central Web Authentication with FlexConnect Access Points was an unsupported configuration until 8.5.100.0. Cisco Bug IDs: CSCve17756.

Weakness: CWE-693 (Protection Mechanism Failure)

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

It affects 1 product.


Products: Cisco Aironet Access Point Software.

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

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

## Is CVE-2018-0250 being exploited?

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

## Other vulnerabilities in Cisco Aironet Access Points

- [CVE-2017-3831](https://insights.sbomify.com/CVE-2017-3831/): Auth bypass in Cisco Mobility Express 1800 Access Point Series (critical 9.8)
- [CVE-2022-20622](https://insights.sbomify.com/CVE-2022-20622/): Cisco Embedded Wireless Controller with Catalyst Access Points IP Flood Denial of Service Vulnerability (high 8.6)
- [CVE-2018-0234](https://insights.sbomify.com/CVE-2018-0234/): Denial of service in Cisco Aironet 1810, 1830, and 1850 Series Access Points (high 8.6)
- [CVE-2016-1419](https://insights.sbomify.com/CVE-2016-1419/): Denial of service in n/a (high 8.1)
- [CVE-2016-6362](https://insights.sbomify.com/CVE-2016-6362/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-0250 is a medium-severity vulnerability in Cisco Aironet Access Points, published on 2 May 2018. 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-2018-0250 in the wild and no public exploit code.

Affected product: Cisco Aironet Access Points. 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-0250/ (Markdown: https://insights.sbomify.com/CVE-2018-0250/index.md)
```

## Sources

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

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