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

> Local attackers can gain root access by bypassing the CLI interface in EMC RecoverPoint for Virtual Machines.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 10 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-53fv-rqv7-v4xm

## What is CVE-2015-4526?

CVE-2015-4526 is a high-severity vulnerability in n/a, published on 10 Jul 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

EMC RecoverPoint for Virtual Machines (VMs) 4.2 allows local users to obtain root-shell access by bypassing the Installation Manager Boxmgmt CLI interface.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Emc Recoverpoint for Virtual Machines.

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

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

## Is CVE-2015-4526 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-4526 is a high-severity vulnerability in n/a, published on 10 Jul 2015. 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-2015-4526 in the wild and no public exploit code.

Affected product: n/a. 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-4526/ (Markdown: https://insights.sbomify.com/CVE-2015-4526/index.md)
```

## Sources

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

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