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

> Local users with specific storage permissions can write to arbitrary files via directory traversal in libvirt when fine-grained ACLs are enabled.

- **Severity:** Low 2.5 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 11 Apr 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-5313, GHSA-qr2q-8mvm-hxvr, MGASA-2016-0103, SUSE-SU-2016:0923-1, SUSE-SU-2016:0931-1, UBUNTU-CVE-2015-5313

## What is CVE-2015-5313?

CVE-2015-5313 is a low-severity path traversal vulnerability in Redhat Libvirt, published on 11 Apr 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Directory traversal vulnerability in the virStorageBackendFileSystemVolCreate function in storage/storage_backend_fs.c in libvirt, when fine-grained Access Control Lists (ACL) are in effect, allows local users with storage_vol:create ACL but not domain:write permission to write to arbitrary files via a .. (dot dot) in a volume name.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libvirt` | SUSE:Linux Enterprise Desktop 11 SP4 | All versions | 1.2.5-12.3 |
| `libvirt` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 1.2.18.2-8.1 |
| `libvirt` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 1.2.5-12.3 |
| `libvirt` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 1.2.18.2-8.1 |
| `libvirt` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 1.2.5-12.3 |
| `libvirt` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.2.18.2-8.1 |
| `libvirt` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 1.2.5-12.3 |
| `libvirt` | SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 1.2.18.2-8.1 |
| `libvirt` | SUSE:Linux Enterprise Workstation Extension 12 SP1 | All versions | 1.2.18.2-8.1 |

Products: Redhat Libvirt.

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

Apply the vendor's patch.

## Is CVE-2015-5313 being exploited?

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

## Other vulnerabilities in Redhat Libvirt

- [CVE-2013-4401](https://insights.sbomify.com/CVE-2013-4401/): Missing authorization in n/a (high 8.5)
- [CVE-2017-2635](https://insights.sbomify.com/CVE-2017-2635/): Null dereference in libvirt (high 7.7)
- [CVE-2013-4400](https://insights.sbomify.com/CVE-2013-4400/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-4291](https://insights.sbomify.com/CVE-2013-4291/): Privilege escalation in n/a (medium 6.9)
- [CVE-2011-1146](https://insights.sbomify.com/CVE-2011-1146/): Missing authorization in n/a (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5313 is a low-severity path traversal vulnerability in Redhat Libvirt, published on 11 Apr 2016. 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-5313 in the wild and no public exploit code.

Affected product: Redhat Libvirt. 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-5313/ (Markdown: https://insights.sbomify.com/CVE-2015-5313/index.md)
```

## Sources

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

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