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

> Remote attackers can read arbitrary files outside the application directory via path traversal in ELOG web application.

- **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:** Yes
- **Published:** 21 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xghq-r485-w5jv

## What is CVE-2006-0347?

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

### Official description

Directory traversal vulnerability in ELOG before 2.6.1 allows remote attackers to access arbitrary files outside of the elog directory via "../" (dot dot) sequences in the URL.

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

It affects 1 product.


Products: Stefan Ritt Elog Web Logbook.

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

Upgrade to a fixed version.

## Is CVE-2006-0347 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5790](https://insights.sbomify.com/CVE-2006-5790/): Memory corruption in n/a (high 7.5)
- [CVE-2006-0597](https://insights.sbomify.com/CVE-2006-0597/): Memory corruption in n/a (high 7.5)
- [CVE-2006-0598](https://insights.sbomify.com/CVE-2006-0598/): Memory corruption in n/a (high 7.5)
- [CVE-2005-0439](https://insights.sbomify.com/CVE-2005-0439/): Memory corruption in n/a (high 7.5)
- [CVE-2005-0440](https://insights.sbomify.com/CVE-2005-0440/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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