# CVE-2007-2836: Path traversal in n/a

> Remote attackers can delete arbitrary files via directory traversal in session IDs, affecting Hiki wiki software.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2007-3395, DEBIAN-CVE-2007-2836, DSA-1324-1, GHSA-cxg5-jqhx-8cv4

## What is CVE-2007-2836?

CVE-2007-2836 is a medium-severity path traversal vulnerability in n/a, published on 2 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in session.rb in Hiki 0.8.0 through 0.8.6 allows remote attackers to delete arbitrary files via directory traversal sequences in the session ID, which is matched against an insufficiently restrictive regular expression before it is used to construct a filename that is marked for deletion at logout.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2007-2836?

It affects 1 product.


Products: Hiki Hiki.

## How do I fix CVE-2007-2836?

Upgrade to a fixed version.

## Is CVE-2007-2836 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2336](https://insights.sbomify.com/CVE-2005-2336/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2005-2803](https://insights.sbomify.com/CVE-2005-2803/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2836 and fix it if it is affected.

What it is: CVE-2007-2836 is a medium-severity path traversal vulnerability in n/a, published on 2 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2836 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-2007-2836/ (Markdown: https://insights.sbomify.com/CVE-2007-2836/index.md)
```

## Sources

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

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