# CVE-2005-1934: Integer overflow in n/a

> Remote attackers can crash the Gaim instant messaging client by sending a malformed MSN message that triggers a large memory allocation.

- **Severity:** Medium 5.0 (`AV:N/AC:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hq79-cp3f-mcr5

## What is CVE-2005-1934?

CVE-2005-1934 is a medium-severity vulnerability in n/a, published on 9 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gaim before 1.3.1 allows remote attackers to cause a denial of service (crash) via a malformed MSN message that leads to a memory allocation of a large size, possibly due to an integer signedness error.

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

It affects 1 product.


Products: Rob Flynn Gaim.

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

Upgrade to a fixed version.

## Is CVE-2005-1934 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-1172](https://insights.sbomify.com/CVE-2000-1172/): Memory corruption in n/a (critical 10.0)
- [CVE-2005-1261](https://insights.sbomify.com/CVE-2005-1261/): Memory corruption in n/a (high 7.5)
- [CVE-2004-0754](https://insights.sbomify.com/CVE-2004-0754/): Integer overflow in n/a (high 7.5)
- [CVE-2004-0784](https://insights.sbomify.com/CVE-2004-0784/): Command injection in n/a (high 7.5)
- [CVE-2004-0785](https://insights.sbomify.com/CVE-2004-0785/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1934 is a medium-severity vulnerability in n/a, published on 9 Jun 2005. 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-2005-1934 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-1934/ (Markdown: https://insights.sbomify.com/CVE-2005-1934/index.md)
```

## Sources

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

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