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

> Local attackers can exploit insecure file creation in the CRIU daemon to create arbitrary files or take ownership of existing files, leading to privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 7 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-5228, GHSA-4j5v-wrcf-qww8

## What is CVE-2015-5228?

CVE-2015-5228 is a high-severity path traversal vulnerability in Opensuse Opensuse, published on 7 Jun 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The service daemon in CRIU creates log and dump files insecurely, which allows local users to create arbitrary files and take ownership of existing files via unspecified vectors related to a directory path.

Weakness: CWE-264

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

It affects 2 products.


Products: Criu Checkpoint\/Restore in Userspace, Opensuse Opensuse.

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

Apply the vendor's patch.

## Is CVE-2015-5228 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2015-5231](https://insights.sbomify.com/CVE-2015-5231/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5228 is a high-severity path traversal vulnerability in Opensuse Opensuse, published on 7 Jun 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-5228 in the wild and no public exploit code.

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

## Sources

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

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