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

> Local attackers can cause a denial of service in nullmailer by sending email to non-existent users, halting mail delivery for all users.

- **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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2002-1313, DSA-198, GHSA-w7cg-654h-r28x

## What is CVE-2002-1313?

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

### Official description

nullmailer 1.00RC5 and earlier allows local users to cause a denial of service via an email to a local user that does not exist, which generates an error that causes nullmailer to stop sending mail to all users.

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

It affects 1 product.


Products: Nullmailer Nullmailer.

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

Upgrade to a fixed version.

## Is CVE-2002-1313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1313 is a low-severity denial of service vulnerability in n/a, published on 1 Sep 2004. 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-2002-1313 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-2002-1313/ (Markdown: https://insights.sbomify.com/CVE-2002-1313/index.md)
```

## Sources

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

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