# CVE-2015-4235: Privilege escalation in n/a

> Remote authenticated users can escalate to root privileges on Cisco APIC and Nexus 9000 ACI devices via the cluster-management configuration feature.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **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:** 24 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vvgq-gww9-5ghc

## What is CVE-2015-4235?

CVE-2015-4235 is a critical vulnerability in Cisco Nx-Os, published on 24 Jul 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cisco Application Policy Infrastructure Controller (APIC) devices with software before 1.0(3o) and 1.1 before 1.1(1j) and Nexus 9000 ACI devices with software before 11.0(4o) and 11.1 before 11.1(1j) do not properly restrict access to the APIC filesystem, which allows remote authenticated users to obtain root privileges via unspecified use of the APIC cluster-management configuration feature, aka Bug IDs CSCuu72094 and CSCuv11991.

Weakness: CWE-264

## Which versions are affected by CVE-2015-4235?

It affects 2 products.


Products: Cisco Application Policy Infrastructure Controller \(Apic\), Cisco Nx-Os.

## How do I fix CVE-2015-4235?

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

## Is CVE-2015-4235 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4235 and fix it if it is affected.

What it is: CVE-2015-4235 is a critical vulnerability in Cisco Nx-Os, published on 24 Jul 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-4235 in the wild and no public exploit code.

Affected product: Cisco Nx-Os. 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-2015-4235/ (Markdown: https://insights.sbomify.com/CVE-2015-4235/index.md)
```

## Sources

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

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