# CVE-2006-5850: Memory corruption in n/a

> Remote attackers can execute arbitrary code on Essentia Web Server via a stack-based buffer overflow triggered by a long URI in GET or HEAD requests.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 10 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p44w-2cfr-qx7x

## What is CVE-2006-5850?

CVE-2006-5850 is a high-severity memory corruption vulnerability in n/a, published on 10 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in Essentia Web Server 2.15 for Windows allows remote attackers to execute arbitrary code via a long URI, as demonstrated by a GET or HEAD request.  NOTE: some of these details are obtained from third party information.

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

It affects 1 product.


Products: Essen Essentia Web Server.

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

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

## Is CVE-2006-5850 being exploited?

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

Public exploit code:

- Essentia Web Server 2.1 - 'URL' Remote Buffer Overflow (exploitdb)
- Essentia Web Server 2.15 - GET Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0313](https://insights.sbomify.com/CVE-2002-0313/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0312](https://insights.sbomify.com/CVE-2002-0312/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5850 is a high-severity memory corruption vulnerability in n/a, published on 10 Nov 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-5850 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-5850/ (Markdown: https://insights.sbomify.com/CVE-2006-5850/index.md)
```

## Sources

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

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