# CVE-2005-2655: Privilege escalation in n/a

> Local attackers can gain elevated privileges by exploiting a privilege dropping failure in maildrop's lockmail utility.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Aug 2005
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2005-2655, DSA-791-1, DTSA-11-1, GHSA-mjj8-2wvx-jfh5

## What is CVE-2005-2655?

CVE-2005-2655 is a critical vulnerability in n/a, published on 30 Aug 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

lockmail in maildrop before 1.5.3 does not drop privileges before executing commands, which allows local users to gain privileges via command line arguments.

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

It affects 1 product.


Products: Maildrop Maildrop.

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

Upgrade to a fixed version.

## Is CVE-2005-2655 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0301](https://insights.sbomify.com/CVE-2010-0301/): Privilege escalation in n/a (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2655 is a critical vulnerability in n/a, published on 30 Aug 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2655 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-2655/ (Markdown: https://insights.sbomify.com/CVE-2005-2655/index.md)
```

## Sources

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

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