# CVE-2004-1688: Denial of service in n/a

> Remote attackers can cause a denial of service via infinite loop and CPU consumption by sending a long login name to 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:** No
- **Published:** 20 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-5wrm-j5hw-2wjj

## What is CVE-2004-1688?

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

### Official description

Pigeon Server 3.02.0143 and earlier allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a long login name sent to port 3103.

## Which versions are affected by CVE-2004-1688?

It affects 1 product.


Products: Tech-Noel Pigeon Server.

## How do I fix CVE-2004-1688?

No fix has been published for CVE-2004-1688 yet. Limit exposure of the affected software until one is available.

## Is CVE-2004-1688 being exploited?

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

Public exploit code:

- Pigeon Server 3.02.0143 - Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1688 and fix it if it is affected.

What it is: CVE-2004-1688 is a medium-severity denial of service vulnerability in n/a, published on 20 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1688 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-2004-1688/ (Markdown: https://insights.sbomify.com/CVE-2004-1688/index.md)
```

## Sources

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

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