# CVE-2006-3798: Other in n/a

> Remote attackers can overwrite global variables via cookies in DeluxeBB, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v99m-464r-x5xg

## What is CVE-2006-3798?

CVE-2006-3798 is a medium-severity vulnerability in n/a, published on 21 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DeluxeBB 1.07 and earlier allows remote attackers to overwrite the (1) _GET, (2) _POST, (3) _ENV, and (4) _SERVER variables via the _COOKIE (aka COOKIE) variable, which can overwrite the other variables during an extract function call, probably leading to multiple security vulnerabilities, aka "pollution of the global namespace."

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

It affects 1 product.


Products: Deluxebb Deluxebb.

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

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

## Is CVE-2006-3798 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6237](https://insights.sbomify.com/CVE-2007-6237/): Auth bypass in n/a (critical 9.0)
- [CVE-2009-4465](https://insights.sbomify.com/CVE-2009-4465/): Information disclosure in n/a (high 7.5)
- [CVE-2009-1033](https://insights.sbomify.com/CVE-2009-1033/): SQL injection in n/a (high 7.5)
- [CVE-2008-2194](https://insights.sbomify.com/CVE-2008-2194/): SQL injection in n/a (high 7.5)
- [CVE-2006-5154](https://insights.sbomify.com/CVE-2006-5154/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3798 is a medium-severity vulnerability in n/a, published on 21 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-3798 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-3798/ (Markdown: https://insights.sbomify.com/CVE-2006-3798/index.md)
```

## Sources

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

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