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

> Local users can access the host filesystem via the mount command in DOSBox, though the vendor disputes this as a security issue.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-6328, GHSA-m882-wm83-jrj3

## What is CVE-2007-6328?

CVE-2007-6328 is a high-severity path traversal vulnerability in n/a, published on 13 Dec 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

DOSBox 0.72 and earlier allows local users to obtain access to the filesystem on the host operating system via the mount command.  NOTE: the researcher reports a vendor response stating that this is not a security problem

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

It affects 1 product.


Products: Dosbox Dosbox.

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

No fix published yet.

## Is CVE-2007-6328 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6328 is a high-severity path traversal vulnerability in n/a, published on 13 Dec 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-6328 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-6328/ (Markdown: https://insights.sbomify.com/CVE-2007-6328/index.md)
```

## Sources

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

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