# CVE-2006-5658: Other in n/a

> Remote attackers can execute arbitrary local files, download files, or delete files via the BlooMooWeb ActiveX control methods.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jjm8-ccwf-56qc

## What is CVE-2006-5658?

CVE-2006-5658 is a high-severity vulnerability in n/a, published on 3 Nov 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

BlooMooWeb ActiveX control (AidemATL.dll) allows remote attackers to (1) download arbitrary files via a URL in the bstrUrl parameter to the BW_DownloadFile method, (2) execute arbitrary local files via a file path in the bstrParams parameter to the BW_LaunchGame method, and (3) delete arbitrary files via a file path in the filePath parameter to the BW_DeleteTempFile method.

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

It affects 1 product.


Products: Studio Achtundachtzig Bloomooweb Activex Control.

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

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

## Is CVE-2006-5658 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5658 is a high-severity vulnerability in n/a, published on 3 Nov 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-5658 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-5658/ (Markdown: https://insights.sbomify.com/CVE-2006-5658/index.md)
```

## Sources

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

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