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

> Attackers can crash the system by providing an invalid address to specific memory management hooks in NGSEC StackDefender.

- **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:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wpm6-cv2v-qgj5

## What is CVE-2004-0766?

CVE-2004-0766 is a medium-severity denial of service vulnerability in n/a, published on 4 Aug 2004. 

### Official description

NGSEC StackDefender 2.0 allows attackers to cause a denial of service (system crash) via an invalid address for the BaseAddress parameter to the hooks for the (1) ZwAllocateVirtualMemory or (2) ZwProtectVirtualMemory functions.

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

It affects 1 product.


Products: Ngsec Stackdefender.

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

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

## Is CVE-2004-0766 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0767](https://insights.sbomify.com/CVE-2004-0767/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0766 is a medium-severity denial of service vulnerability in n/a, published on 4 Aug 2004. 
Exploitation: There is no known exploitation of CVE-2004-0766 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-2004-0766/ (Markdown: https://insights.sbomify.com/CVE-2004-0766/index.md)
```

## Sources

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

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