# CVE-2005-0875: Memory corruption in n/a

> Remote attackers can crash the Trillian instant messenger application by sending a long string in an HTTP response header via a malicious web server.

- **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:** No
- **Published:** 26 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rf2r-3p8v-h284

## What is CVE-2005-0875?

CVE-2005-0875 is a medium-severity memory corruption vulnerability in n/a, published on 26 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in the Yahoo plug-in for Trillian 2.0, 3.0, and 3.1 allow remote web servers to cause a denial of service (application crash) via a long string in an HTTP 1.1 response header.

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

It affects 1 product.


Products: Cerulean Studios Trillian.

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

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

## Is CVE-2005-0875 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5401](https://insights.sbomify.com/CVE-2008-5401/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-5402](https://insights.sbomify.com/CVE-2008-5402/): Use after free in n/a (critical 10.0)
- [CVE-2008-5403](https://insights.sbomify.com/CVE-2008-5403/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-2390](https://insights.sbomify.com/CVE-2002-2390/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-2409](https://insights.sbomify.com/CVE-2008-2409/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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