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

> Local attackers can crash ICQ 2003b by exploiting a heap-based buffer overflow in the Answering Service function via registry values.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hjfj-5586-j3hv

## What is CVE-2006-5724?

CVE-2006-5724 is a low-severity memory corruption vulnerability in n/a, published on 4 Nov 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Heap-based buffer overflow the "Answering Service" function in ICQ 2003b Build 3916 allows local users to cause a denial of service (application crash) via a long string in the "AwayMsg Presets" value in the ICQ\ICQPro\DefaultPrefs\Presets registry key.

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

It affects 1 product.


Products: Mirabilis Icq.

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

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

## Is CVE-2006-5724 being exploited?

There is no known exploitation of CVE-2006-5724 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-2006-4662](https://insights.sbomify.com/CVE-2006-4662/): Memory corruption in n/a (high 7.5)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5724 is a low-severity memory corruption vulnerability in n/a, published on 4 Nov 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-5724 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-5724/ (Markdown: https://insights.sbomify.com/CVE-2006-5724/index.md)
```

## Sources

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

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