# CVE-2005-4693: Denial of service in n/a

> Remote attackers can crash Gaim-Encryption via crafted ICQ messages, requiring an upgrade to mitigate the denial of service risk.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2006
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7rqv-hpgx-m2wc

## What is CVE-2005-4693?

CVE-2005-4693 is a medium-severity denial of service vulnerability in n/a, published on 1 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gaim-Encryption 2.38-1 on Debian Linux allows remote attackers to cause a denial of service (crash) via a crafted message from an ICQ buddy, possibly involving the GE_received_key function in keys.c.

## Which versions are affected by CVE-2005-4693?

It affects 1 product.


Products: Gaim-Encryption Gaim-Encryption.

## How do I fix CVE-2005-4693?

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

## Is CVE-2005-4693 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0163](https://insights.sbomify.com/CVE-2003-0163/): Integer overflow in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4693 and fix it if it is affected.

What it is: CVE-2005-4693 is a medium-severity denial of service vulnerability in n/a, published on 1 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4693 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-2005-4693/ (Markdown: https://insights.sbomify.com/CVE-2005-4693/index.md)
```

## Sources

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

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