# CVE-2015-6927: Path traversal in n/a

> Local container root users can exploit symlink handling to change passwords for arbitrary ploop containers, leading to privilege escalation and control panel access.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:N/I:P/A:P`)
- **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 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-3357-1, GHSA-h76c-22cc-xhhx

## What is CVE-2015-6927?

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

### Official description

vzctl before 4.9.4 determines the virtual environment (VE) layout based on the presence of root.hdd/DiskDescriptor.xml in the VE private directory, which allows local simfs container (CT) root users to change the root password for arbitrary ploop containers, as demonstrated by a symlink attack on the ploop container root.hdd file and then access a control panel.

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

## Which versions are affected by CVE-2015-6927?

It affects 1 product.


Products: Openvz Vzctl.

## How do I fix CVE-2015-6927?

Upgrade to a fixed version.

## Is CVE-2015-6927 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6927 and fix it if it is affected.

What it is: CVE-2015-6927 is a low-severity path traversal vulnerability in n/a, published on 28 Sep 2015. 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-2015-6927 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-2015-6927/ (Markdown: https://insights.sbomify.com/CVE-2015-6927/index.md)
```

## Sources

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

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