# CVE-2010-0301: Privilege escalation in n/a

> Local attackers can gain root privileges by exploiting improper privilege handling in maildrop when executed with the -d option.

- **Severity:** Medium 6.9 (`AV:L/AC:M/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:** 4 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-0301, DSA-1981-1, GHSA-7mg2-6qgr-3p64

## What is CVE-2010-0301?

CVE-2010-0301 is a medium-severity vulnerability in n/a, published on 4 Feb 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

main.C in maildrop 2.3.0 and earlier, when run by root with the -d option, uses the gid of root for execution of the .mailfilter file in a user's home directory, which allows local users to gain privileges via a crafted file.

Weakness: CWE-264

## Which versions are affected by CVE-2010-0301?

It affects 1 product.


Products: Maildrop Maildrop.

## How do I fix CVE-2010-0301?

Apply the vendor's patch.

## Is CVE-2010-0301 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2655](https://insights.sbomify.com/CVE-2005-2655/): Privilege escalation in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0301 and fix it if it is affected.

What it is: CVE-2010-0301 is a medium-severity vulnerability in n/a, published on 4 Feb 2010. 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-2010-0301 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-2010-0301/ (Markdown: https://insights.sbomify.com/CVE-2010-0301/index.md)
```

## Sources

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

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