# CVE-2006-1941: Denial of service in n/a

> Remote attackers can cause a denial of service in Neon Responder by sending a crafted Clock Synchronisation packet.

- **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 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6rf3-vvj3-mjpf

## What is CVE-2006-1941?

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

### Official description

Neon Responder 5.4 for LANsurveyor allows remote attackers to cause a denial of service (application outage) via a crafted Clock Synchronisation packet that triggers an access violation.

## Which versions are affected by CVE-2006-1941?

It affects 1 product.


Products: Neon Software Neon Responder.

## How do I fix CVE-2006-1941?

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

## Is CVE-2006-1941 being exploited?

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

Public exploit code:

- Neon Responders 5.4 - Remote Clock Synchronization Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1941 and fix it if it is affected.

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

## Sources

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

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