# CVE-2005-0635: Buffer overflow in Foxmail Server 2.0 allows remote attackers to execute arbitrary code via a long USER command.


- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f992-pf55-46rq

## What is CVE-2005-0635?

CVE-2005-0635 is a critical vulnerability in n/a, published on 4 Mar 2005. 

### Official description

Buffer overflow in Foxmail Server 2.0 allows remote attackers to execute arbitrary code via a long USER command.

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

It affects 1 product.


Products: Foxmail Foxmail Email Server.

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

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

## Is CVE-2005-0635 being exploited?

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

Public exploit code:

- Foxmail 1.1.0.1 - POP3 Temp Dir Stack Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0636](https://insights.sbomify.com/CVE-2005-0636/): Other in n/a (critical 10.0)
- [CVE-2005-0339](https://insights.sbomify.com/CVE-2005-0339/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0635 is a critical vulnerability in n/a, published on 4 Mar 2005. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0635 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-2005-0635/ (Markdown: https://insights.sbomify.com/CVE-2005-0635/index.md)
```

## Sources

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

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