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

> Remote attackers can cause a denial of service in Courier MTA by sending messages with invalid year values, leading to CPU exhaustion.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2002-0914, GHSA-2fx9-2g54-566x

## What is CVE-2002-0914?

CVE-2002-0914 is a medium-severity denial of service vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Double Precision Courier e-mail MTA allows remote attackers to cause a denial of service (CPU consumption) via a message with an extremely large or negative value for the year, which causes a tight loop.

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

It affects 1 product.


Products: Double Precision Incorporated Courier Mta.

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

Upgrade to a fixed version.

## Is CVE-2002-0914 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2659](https://insights.sbomify.com/CVE-2006-2659/): Denial of service in n/a (high 7.8)
- [CVE-2003-0040](https://insights.sbomify.com/CVE-2003-0040/): SQL injection in n/a (high 7.5)
- [CVE-2004-0224](https://insights.sbomify.com/CVE-2004-0224/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1311](https://insights.sbomify.com/CVE-2002-1311/): Information disclosure in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0914 is a medium-severity denial of service vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0914 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-0914/ (Markdown: https://insights.sbomify.com/CVE-2002-0914/index.md)
```

## Sources

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

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