# CVE-2008-1920: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause a crash in ICQ by sending a crafted personal status message.

- **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:** 22 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x26f-cv2q-rg6c

## What is CVE-2008-1920?

CVE-2008-1920 is a high-severity memory corruption vulnerability in n/a, published on 22 Apr 2008. 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

Heap-based buffer overflow in the boxelyRenderer module in the Personal Status Manager feature in ICQ 6.0 build 6043 allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a crafted personal status message.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-1920?

It affects 1 product.


Products: Icq Mirabilis Icq.

## How do I fix CVE-2008-1920?

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

## Is CVE-2008-1920 being exploited?

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

Public exploit code:

- ICQ 6 - 'Personal Status Manager' Remote Buffer Overflow (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-1120](https://insights.sbomify.com/CVE-2008-1120/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1920 and fix it if it is affected.

What it is: CVE-2008-1920 is a high-severity memory corruption vulnerability in n/a, published on 22 Apr 2008. 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-2008-1920 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-2008-1920/ (Markdown: https://insights.sbomify.com/CVE-2008-1920/index.md)
```

## Sources

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

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