# CVE-2021-29149: Security feature bypass in Aruba CX 6200F Switch Series, Aruba 6300 Switch Series, Aruba 6400 Switch Series, Aruba 8320 Switch Series, Aruba 8325 Switch Series, Aruba 8400 Switch Series, Aruba CX 8360 Switch Series

> A local attacker can bypass security restrictions on Aruba CX switches, requiring firmware upgrades to mitigate.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wfq6-vc3m-f5f7

## What is CVE-2021-29149?

CVE-2021-29149 is a medium-severity vulnerability in Aruba CX 6200F Switch Series, Aruba 6300 Switch Series, Aruba 6400 Switch Series, Aruba 8320 Switch Series, Aruba 8325 Switch Series, Aruba 8400 Switch Series, Aruba CX 8360 Switch Series, published on 22 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A local bypass security restrictions vulnerability was discovered in Aruba CX 6200F Switch Series, Aruba 6300 Switch Series, Aruba 6400 Switch Series, Aruba 8320 Switch Series, Aruba 8325 Switch Series, Aruba 8400 Switch Series, Aruba CX 8360 Switch Series version(s): Aruba AOS-CX firmware: 10.04.xxxx - versions prior to 10.04.3070, 10.05.xxxx - versions prior to 10.05.0070, 10.06.xxxx - versions prior to 10.06.0110, 10.07.xxxx - versions prior to 10.07.0001. Aruba has released upgrades for Aruba AOS-CX devices that address this security vulnerability.

## Which versions are affected by CVE-2021-29149?

It affects 1 product.


Products: Arubanetworks Aos-Cx Firmware.

## How do I fix CVE-2021-29149?

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

## Is CVE-2021-29149 being exploited?

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

## Other vulnerabilities in Aruba CX 6200F Switch Series, Aruba 6300 Switch Series, Aruba 6400 Switch Series, Aruba 8320 Switch Series, Aruba 8325 Switch Series, Aruba 8400 Switch Series, Aruba CX 8360 Switch Series

- [CVE-2021-29143](https://insights.sbomify.com/CVE-2021-29143/): Command injection in Aruba CX 6200F Switch Series, Aruba 6300 Switch Series, Aruba 6400 Switch Series, Aruba 8320 Switch Series, Aruba 8325 Switch Series, Aruba 8400 Switch Series, Aruba CX 8360 Switch Series (high 7.2)
- [CVE-2021-29148](https://insights.sbomify.com/CVE-2021-29148/): Cross-site scripting in Aruba CX 6200F Switch Series, Aruba 6300 Switch Series, Aruba 6400 Switch Series, Aruba 8320 Switch Series, Aruba 8325 Switch Series, Aruba 8400 Switch Series, Aruba CX 8360 Switch Series (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29149 and fix it if it is affected.

What it is: CVE-2021-29149 is a medium-severity vulnerability in Aruba CX 6200F Switch Series, Aruba 6300 Switch Series, Aruba 6400 Switch Series, Aruba 8320 Switch Series, Aruba 8325 Switch Series, Aruba 8400 Switch Series, Aruba CX 8360 Switch Series, published on 22 Jul 2021. 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-2021-29149 in the wild and no public exploit code.

Affected product: Aruba CX 6200F Switch Series, Aruba 6300 Switch Series, Aruba 6400 Switch Series, Aruba 8320 Switch Series, Aruba 8325 Switch Series, Aruba 8400 Switch Series, Aruba CX 8360 Switch Series. 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-2021-29149/ (Markdown: https://insights.sbomify.com/CVE-2021-29149/index.md)
```

## Sources

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

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