# CVE-2008-6933: Path traversal in n/a

> Remote attackers can read source code and other files via directory traversal in MiniGal, exposing sensitive application data.

- **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:** 11 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-48m4-gq2m-xcx4

## What is CVE-2008-6933?

CVE-2008-6933 is a medium-severity path traversal vulnerability in n/a, published on 11 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in index.php in MiniGal b13 (aka MG2) allows remote attackers to read the source code of .php files, and possibly the content of other files, via a .. (dot dot) in the list parameter.

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

## Which versions are affected by CVE-2008-6933?

It affects 1 product.


Products: Minigal Minigal.

## How do I fix CVE-2008-6933?

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

## Is CVE-2008-6933 being exploited?

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

Public exploit code:

- Minigal b13 - Remote File Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2145](https://insights.sbomify.com/CVE-2007-2145/): Code injection in n/a (high 7.5)
- [CVE-2007-2146](https://insights.sbomify.com/CVE-2007-2146/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6933 and fix it if it is affected.

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

## Sources

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

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