# CVE-2006-4662: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a heap-based buffer overflow in the ICQ client's message parsing function.

- **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:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-536r-fjf3-3wp7

## What is CVE-2006-4662?

CVE-2006-4662 is a high-severity memory corruption vulnerability in n/a, published on 9 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in the MCRegEx__Search function in AOL ICQ Pro 2003b Build 3916 and earlier allows remote attackers to execute arbitrary code via an inconsistent length field of a Message in a 0x2711 Type-Length-Value (TLV) type.

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

It affects 1 product.


Products: Mirabilis Icq.

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

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

## Is CVE-2006-4662 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2329](https://insights.sbomify.com/CVE-2002-2329/): Denial of service in n/a (high 7.8)
- [CVE-2003-0235](https://insights.sbomify.com/CVE-2003-0235/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0236](https://insights.sbomify.com/CVE-2003-0236/): Integer overflow in n/a (high 7.5)
- [CVE-2003-0237](https://insights.sbomify.com/CVE-2003-0237/): Supply chain in n/a (high 7.5)
- [CVE-2002-0028](https://insights.sbomify.com/CVE-2002-0028/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4662 is a high-severity memory corruption vulnerability in n/a, published on 9 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4662 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-4662/ (Markdown: https://insights.sbomify.com/CVE-2006-4662/index.md)
```

## Sources

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

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