# CVE-2024-20510: Auth bypass in Cisco IOS XE Software

> Unauthenticated adjacent attackers can bypass pre-authentication ACLs on Cisco IOS XE Wireless Controllers, gaining unauthorized access to trusted networks.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **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:** 25 Sep 2024
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-pp73-8587-cg75

## What is CVE-2024-20510?

CVE-2024-20510 is a medium-severity authentication bypass vulnerability in Cisco Ios Xe, published on 25 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the Central Web Authentication (CWA) feature of Cisco IOS XE Software for Wireless Controllers could allow an unauthenticated, adjacent attacker to bypass the pre-authentication access control list (ACL), which could allow access to network resources before user authentication.

 This vulnerability is due to a logic error when activating the pre-authentication ACL that is received from the authentication, authorization, and accounting (AAA) server. An attacker could exploit this vulnerability by connecting to a wireless network that is configured for CWA and sending traffic through an affected device that should be denied by the configured ACL before user authentication. A successful exploit could allow the attacker to bypass configured ACL protections on the affected device before the user authentication is completed, allowing the attacker to access trusted networks that the device might be protecting.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-20510?

It affects 1 product.


Products: Cisco Ios Xe.

## How do I fix CVE-2024-20510?

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

## Is CVE-2024-20510 being exploited?

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

## Other vulnerabilities in Cisco Ios Xe

- [CVE-2023-20198](https://insights.sbomify.com/CVE-2023-20198/): Cisco IOS XE Web UI Privilege Escalation (critical 10.0, exploited in the wild)
- [CVE-2018-0151](https://insights.sbomify.com/CVE-2018-0151/): Cisco IOS Software and Cisco IOS XE Software Quality of Service Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2023-20273](https://insights.sbomify.com/CVE-2023-20273/): Cisco IOS XE Web UI Command Injection (high 7.2, exploited in the wild)
- [CVE-2025-20188](https://insights.sbomify.com/CVE-2025-20188/): Hardcoded credentials in Cisco IOS XE Software (critical 10.0)
- [CVE-2021-34770](https://insights.sbomify.com/CVE-2021-34770/): Cisco IOS XE Software for Catalyst 9000 Family Wireless Controllers CAPWAP Remote Code Execution Vulnerability (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20510 and fix it if it is affected.

What it is: CVE-2024-20510 is a medium-severity authentication bypass vulnerability in Cisco Ios Xe, published on 25 Sep 2024. 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-2024-20510 in the wild and no public exploit code.

Affected product: Cisco Ios Xe. 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-2024-20510/ (Markdown: https://insights.sbomify.com/CVE-2024-20510/index.md)
```

## Sources

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

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