# CVE-2005-1911: Denial of service in n/a

> Remote NNTP servers can cause the leafnode fetchnews client to hang, resulting in a denial of service and potential news loss.

- **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:** 8 Jun 2005
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2005-1911, GHSA-g92w-h4gx-4m3r

## What is CVE-2005-1911?

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

### Official description

The fetchnews NNTP client in leafnode 1.11.2 and earlier can hang while waiting for input that never arrives, which allows remote NNTP servers to cause a denial of service (news loss).

## Which versions are affected by CVE-2005-1911?

It affects 1 product.


Products: Leafnode Leafnode.

## How do I fix CVE-2005-1911?

Upgrade to a fixed version.

## Is CVE-2005-1911 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1661](https://insights.sbomify.com/CVE-2002-1661/): Denial of service in n/a (medium 5.0)
- [CVE-2004-2068](https://insights.sbomify.com/CVE-2004-2068/): Denial of service in n/a (medium 5.0)
- [CVE-2005-1453](https://insights.sbomify.com/CVE-2005-1453/): Denial of service in n/a (medium 5.0)
- [CVE-2003-0744](https://insights.sbomify.com/CVE-2003-0744/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1911 and fix it if it is affected.

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

## Sources

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

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