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

> Local attackers can truncate arbitrary files via symlink attacks on temporary files in Xen monitoring tools, requiring local access.

- **Severity:** Medium 6.0 (`AV:L/AC:M/Au:S/C:N/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1395-1, GHSA-cf5w-7gqx-4gh9

## What is CVE-2007-3919?

CVE-2007-3919 is a medium-severity path traversal vulnerability in n/a, published on 28 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

(1) xenbaked and (2) xenmon.py in Xen 3.1 and earlier allow local users to truncate arbitrary files via a symlink attack on /tmp/xenq-shm.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Xensource Inc Xen.

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

Apply the vendor's patch.

## Is CVE-2007-3919 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4993](https://insights.sbomify.com/CVE-2007-4993/): Command injection in n/a (medium 6.9)
- [CVE-2007-5906](https://insights.sbomify.com/CVE-2007-5906/): Denial of service in n/a (medium 4.7)
- [CVE-2007-5907](https://insights.sbomify.com/CVE-2007-5907/): Privilege escalation in n/a (medium 4.7)
- [CVE-2008-1619](https://insights.sbomify.com/CVE-2008-1619/): The ssm_i emulation in Xen 5.1 on IA64 architectures allows attackers to cause a denial of service (dom0 panic) via certain traffic, as demo (medium 4.3)
- [CVE-2007-6207](https://insights.sbomify.com/CVE-2007-6207/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3919 is a medium-severity path traversal vulnerability in n/a, published on 28 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-3919 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-3919/ (Markdown: https://insights.sbomify.com/CVE-2007-3919/index.md)
```

## Sources

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

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