# CVE-2009-0769: Denial of service in n/a

> Remote attackers can cause a denial of service in QIP 2005 by sending a crafted Rich Text Format ICQ message, potentially affecting users of this instant messenger.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/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:** 3 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c2px-jjjp-g9r6

## What is CVE-2009-0769?

CVE-2009-0769 is a medium-severity denial of service vulnerability in n/a, published on 3 Mar 2009. 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

QIP 2005 build 8082 allows remote attackers to cause a denial of service (CPU consumption and application hang) via a crafted Rich Text Format (RTF) ICQ message, as demonstrated by an {\rtf\pict\&&} message.  NOTE: the vulnerability may be in Sergey Tkachenko TRichView. If so, then this should not be treated as a vulnerability in QIP.

Weakness: CWE-399

## Which versions are affected by CVE-2009-0769?

It affects 1 product.


Products: Qip Qip.

## How do I fix CVE-2009-0769?

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

## Is CVE-2009-0769 being exploited?

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

Public exploit code:

- QIP 2005 - Malformed Rich Text Message Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0769 and fix it if it is affected.

What it is: CVE-2009-0769 is a medium-severity denial of service vulnerability in n/a, published on 3 Mar 2009. 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-2009-0769 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-2009-0769/ (Markdown: https://insights.sbomify.com/CVE-2009-0769/index.md)
```

## Sources

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

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