# CVE-2006-2154: Privilege escalation in n/a

> Local attackers can execute arbitrary code with elevated privileges by exploiting a failure to drop privileges during file operations in EMC Retrospect.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5jfv-q796-mg9p

## What is CVE-2006-2154?

CVE-2006-2154 is a high-severity vulnerability in n/a, published on 3 May 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

EMC Retrospect for Windows 6.5 before 6.5.382, 7.0 before 7.0.344, and 7.5 before 7.5.1.105 does not drop privileges before opening files, which allows local users to execute arbitrary code via the File>Open dialog.

## Which versions are affected by CVE-2006-2154?

It affects 1 product.


Products: Emc Retrospect.

## How do I fix CVE-2006-2154?

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

## Is CVE-2006-2154 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2155](https://insights.sbomify.com/CVE-2006-2155/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2154 and fix it if it is affected.

What it is: CVE-2006-2154 is a high-severity vulnerability in n/a, published on 3 May 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-2154 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-2006-2154/ (Markdown: https://insights.sbomify.com/CVE-2006-2154/index.md)
```

## Sources

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

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