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

> Remote attackers can read arbitrary source code from Lighttpd on Windows by appending dots or spaces to filenames, bypassing extension checks.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 6 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pcg2-3652-5c3v

## What is CVE-2006-0814?

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

### Official description

response.c in Lighttpd 1.4.10 and possibly previous versions, when run on Windows, allows remote attackers to read arbitrary source code via requests that contain trailing (1) "." (dot) and (2) space characters, which are ignored by Windows, as demonstrated by PHP files.

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

It affects 1 product.


Products: Lighttpd Lighttpd.

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

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

## Is CVE-2006-0814 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-11072](https://insights.sbomify.com/CVE-2019-11072/): Integer overflow in n/a (critical 9.8)
- [CVE-2007-3949](https://insights.sbomify.com/CVE-2007-3949/): Security feature bypass in n/a (high 8.3)
- [CVE-2007-1870](https://insights.sbomify.com/CVE-2007-1870/): Null dereference in n/a (high 7.8)
- [CVE-2022-30780](https://insights.sbomify.com/CVE-2022-30780/): Denial of service in n/a (high 7.5)
- [CVE-2025-12642](https://insights.sbomify.com/CVE-2025-12642/): HTTP Header Smuggling via Trailer Merge (medium 6.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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