# CVE-2006-2511: File upload in n/a

> Authenticated users can execute arbitrary code by uploading files with unassociated extensions and using the Open With dialog.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rpg2-hv7v-v69f

## What is CVE-2006-2511?

CVE-2006-2511 is a medium-severity vulnerability in n/a, published on 22 May 2006. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The ActiveX version of FrontRange iHEAT allows remote authenticated users to run arbitrary programs or access arbitrary files on the host machine by uploading a file with an extension that is not associated with an application, and selecting a file from the "Open With..." dialog.

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

It affects 1 product.


Products: Frontrange Iheat.

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

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

## Is CVE-2006-2511 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2511 is a medium-severity vulnerability in n/a, published on 22 May 2006. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-2511 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-2511/ (Markdown: https://insights.sbomify.com/CVE-2006-2511/index.md)
```

## Sources

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

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