# CVE-2004-1666: Memory corruption in n/a

> Remote MSN servers can execute arbitrary code on Trillian clients via a buffer overflow in the MSN module.

- **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:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g2gh-64hj-766p

## What is CVE-2004-1666?

CVE-2004-1666 is a high-severity memory corruption vulnerability in n/a, published on 20 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the MSN module in Trillian 0.74i allows remote MSN servers to execute arbitrary code via a long string that ends in a newline character.

## Which versions are affected by CVE-2004-1666?

It affects 1 product.


Products: Cerulean Studios Trillian.

## How do I fix CVE-2004-1666?

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

## Is CVE-2004-1666 being exploited?

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

Public exploit code:

- Trillian 0.74i MSN Module - Remote Buffer Overflow (exploitdb)

## 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-2004-1666 and fix it if it is affected.

What it is: CVE-2004-1666 is a high-severity memory corruption vulnerability in n/a, published on 20 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1666 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-2004-1666/ (Markdown: https://insights.sbomify.com/CVE-2004-1666/index.md)
```

## Sources

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

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