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

> Remote authenticated users can cause a denial of service in NuFW by flooding packets to the authentication server due to improper TLS socket handling.

- **Severity:** Low 1.7 (`AV:L/AC:L/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p49v-cm65-vvrx

## What is CVE-2006-0956?

CVE-2006-0956 is a low-severity denial of service vulnerability in n/a, published on 2 Mar 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

nuauth in NuFW before 1.0.21 does not properly handle blocking TLS sockets, which allows remote authenticated users to cause a denial of service (service hang) by flooding packets at the authentication server.

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

It affects 1 product.


Products: Nufw Nufw Firewall.

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

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

## Is CVE-2006-0956 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0956 is a low-severity denial of service vulnerability in n/a, published on 2 Mar 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0956 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-2006-0956/ (Markdown: https://insights.sbomify.com/CVE-2006-0956/index.md)
```

## Sources

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

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