# CVE-2003-0251: Denial of service in n/a

> Remote attackers can cause a denial of service in ypserv NIS server by sending TCP requests that do not respond, blocking the server.

- **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:** 28 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0251, GHSA-7xw4-2hf3-hvxx

## What is CVE-2003-0251?

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

### Official description

ypserv NIS server before 2.7 allows remote attackers to cause a denial of service via a TCP client request that does not respond to the server, which causes ypserv to block.

## Which versions are affected by CVE-2003-0251?

It affects 1 product.


Products: Nis Ypserv Nis Server.

## How do I fix CVE-2003-0251?

Upgrade to a fixed version.

## Is CVE-2003-0251 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0251 and fix it if it is affected.

What it is: CVE-2003-0251 is a medium-severity denial of service vulnerability in n/a, published on 28 Jun 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-2003-0251 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-2003-0251/ (Markdown: https://insights.sbomify.com/CVE-2003-0251/index.md)
```

## Sources

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

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