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

> Remote authenticated users can crash the IMail IMAP server via a stack-based buffer overflow in the SELECT command.

- **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:** 25 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xcpq-wff2-vp7h

## What is CVE-2005-1254?

CVE-2005-1254 is a medium-severity memory corruption vulnerability in n/a, published on 25 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Stack-based buffer overflow in the IMAP server for Ipswitch IMail 8.12 and 8.13, and other versions before IMail Server 8.2 Hotfix 2, allows remote authenticated users to cause a denial of service (crash) via a SELECT command with a large argument.

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

It affects 1 product.


Products: Ipswitch Imail.

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

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

## Is CVE-2005-1254 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1255](https://insights.sbomify.com/CVE-2005-1255/): Memory corruption in n/a (critical 10.0)
- [CVE-2005-1256](https://insights.sbomify.com/CVE-2005-1256/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0297](https://insights.sbomify.com/CVE-2004-0297/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-0777](https://insights.sbomify.com/CVE-2002-0777/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-1046](https://insights.sbomify.com/CVE-1999-1046/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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