# CVE-2006-5650: Code injection in n/a

> Remote attackers can execute arbitrary code via the ICQPhone ActiveX control's DownloadAgent function, requiring user interaction to trigger the vulnerability.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 7 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wvxp-m3jj-9gmh

## What is CVE-2006-5650?

CVE-2006-5650 is a high-severity code injection vulnerability in n/a, published on 7 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

The ICQPhone.SipxPhoneManager ActiveX control in America Online ICQ 5.1 allows remote attackers to download and execute arbitrary code via the DownloadAgent function, as demonstrated using an ICQ avatar.

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

It affects 1 product.


Products: Aol Icq.

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

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

## Is CVE-2006-5650 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5650 exists.

Public exploit code:

- America Online ICQ 5.1 - ActiveX Control Remote Code Execution (exploitdb)
- America Online ICQ ActiveX Control Arbitrary File Download and Execute (metasploit)
- America Online ICQ - ActiveX Control Arbitrary File Download and Execute (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-1904](https://insights.sbomify.com/CVE-2007-1904/): Path traversal in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5650 is a high-severity code injection vulnerability in n/a, published on 7 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5650 exists.

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-5650/ (Markdown: https://insights.sbomify.com/CVE-2006-5650/index.md)
```

## Sources

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

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