# CVE-2017-12230: Privilege escalation in Cisco IOS XE

> Authenticated attackers can elevate privileges on Cisco IOS XE devices by exploiting incorrect default permissions in the web UI.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xg78-wwf5-gc23

## What is CVE-2017-12230?

CVE-2017-12230 is a high-severity vulnerability in Cisco Ios Xe, published on 28 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the web-based user interface (web UI) of Cisco IOS XE 16.2 could allow an authenticated, remote attacker to elevate their privileges on an affected device. The vulnerability is due to incorrect default permission settings for new users who are created by using the web UI of the affected software. An attacker could exploit this vulnerability by using the web UI of the affected software to create a new user and then logging into the web UI as the newly created user. A successful exploit could allow the attacker to elevate their privileges on the affected device. This vulnerability affects Cisco devices that are running a vulnerable release Cisco IOS XE Software, if the HTTP Server feature is enabled for the device. The newly redesigned, web-based administration UI was introduced in the Denali 16.2 Release of Cisco IOS XE Software. This vulnerability does not affect the web-based administration UI in earlier releases of Cisco IOS XE Software. Cisco Bug IDs: CSCuy83062.

Weakness: CWE-276 (Incorrect Default Permissions), CWE-264

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

It affects 1 product.


Products: Cisco Ios Xe.

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

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

## Is CVE-2017-12230 being exploited?

There is no known exploitation of CVE-2017-12230 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-2017-12230 and fix it if it is affected.

What it is: CVE-2017-12230 is a high-severity vulnerability in Cisco Ios Xe, published on 28 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12230 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-2017-12230/ (Markdown: https://insights.sbomify.com/CVE-2017-12230/index.md)
```

## Sources

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

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