# CVE-2006-1102: Path traversal in n/a

> Remote attackers can cause client denial of service by forcing the server to load a map file with path traversal sequences.

- **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:** 9 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qqqc-468g-2xm4

## What is CVE-2006-1102?

CVE-2006-1102 is a medium-severity path traversal vulnerability in n/a, published on 9 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sauerbraten 2006_02_28, as derived from the Cube engine, allows remote attackers to cause a denial of service (client exit) by forcing the server to change to a map (ogz) file whose name contains ".." sequences and has a certain length that prevents the addition of the ".ogz" extension.

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

It affects 2 products.


Products: Sauerbraten Cube, Sauerbraten Sauerbraten.

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

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

## Is CVE-2006-1102 being exploited?

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

Public exploit code:

- Sauerbraten 2006_02_28 - Multiple Buffer Overflow / Crash (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-1100](https://insights.sbomify.com/CVE-2006-1100/): Memory corruption in n/a (high 7.5)
- [CVE-2006-1101](https://insights.sbomify.com/CVE-2006-1101/): Denial of service in n/a (medium 5.0)
- [CVE-2006-1103](https://insights.sbomify.com/CVE-2006-1103/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1102 is a medium-severity path traversal vulnerability in n/a, published on 9 Mar 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-1102 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-1102/ (Markdown: https://insights.sbomify.com/CVE-2006-1102/index.md)
```

## Sources

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

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