# CVE-2002-1827: Denial of service in n/a

> Local attackers can cause a denial of service in Sendmail by locking critical alias, map, statistics, and pid files.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **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:** 28 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2002-1827, GHSA-rrx8-8c33-99fc

## What is CVE-2002-1827?

CVE-2002-1827 is a low-severity denial of service vulnerability in n/a, published on 28 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sendmail 8.9.0 through 8.12.3 allows local users to cause a denial of service by obtaining an exclusive lock on the (1) alias, (2) map, (3) statistics, and (4) pid files.

## Which versions are affected by CVE-2002-1827?

It affects 1 product.


Products: Sendmail Sendmail.

## How do I fix CVE-2002-1827?

Upgrade to a fixed version.

## Is CVE-2002-1827 being exploited?

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

Public exploit code:

- Sendmail 8.9.x/8.10.x/8.11.x/8.12.x - File Locking Denial of Service (1) (exploitdb)
- Sendmail 8.9.x/8.10.x/8.11.x/8.12.x - File Locking Denial of Service (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2246](https://insights.sbomify.com/CVE-2007-2246/): Denial of service in n/a (high 7.8)
- [CVE-2006-0058](https://insights.sbomify.com/CVE-2006-0058/): Race condition in n/a (high 7.6)
- [CVE-2009-4565](https://insights.sbomify.com/CVE-2009-4565/): Security feature bypass in n/a (high 7.5)
- [CVE-2002-2261](https://insights.sbomify.com/CVE-2002-2261/): Security feature bypass in n/a (high 7.5)
- [CVE-1999-1592](https://insights.sbomify.com/CVE-1999-1592/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1827 and fix it if it is affected.

What it is: CVE-2002-1827 is a low-severity denial of service vulnerability in n/a, published on 28 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1827 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-2002-1827/ (Markdown: https://insights.sbomify.com/CVE-2002-1827/index.md)
```

## Sources

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

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