CVE-2015-5228
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe CRIU (Checkpoint/Restore in Userspace) service daemon creates log and dump files with insecure permissions and potentially in unsafe directory paths, allowing local unprivileged users to create arbitrary files or take ownership of existing files on the system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 13.2all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if CRIU is installedRun 'rpm -qa | grep -i criu' on RPM-based systems or 'dpkg -l | grep -i criu' on Debian-based systems. On openSUSE 13.2, use 'rpm -qa | grep -i criu'Affected if CRIU package is installed and version is any version (all versions affected per the CVE advisory)
-
Verify CRIU daemon service statusRun 'systemctl status criu' or check for criu daemon process with 'ps aux | grep criu'Affected if CRIU daemon is running as a service, as the vulnerability specifically affects the daemon creating files with insecure permissions
-
Identify CRIU log and dump file locationsCheck CRIU configuration files in /etc/criu/ and look for log file paths. Default locations may include /var/log/criu/ or the current working directory of the daemon. Also check systemd service file for any --log or --dump paths specifiedAffected if Log or dump directories exist and are writable by the criu service user
-
Inspect permissions on CRIU log/dump filesRun 'ls -la' on identified log and dump directories. Check if files are created with world-writable permissions (e.g., 666) or with ownership that could be exploitedAffected if Files are created with overly permissive access (world-readable/writable) or with ownership that could be leveraged by unprivileged users
-
Check directory path safety for file creationExamine if CRIU daemon creates files in shared/tmp directories (e.g., /tmp, /var/tmp) where unprivileged users can manipulate file creationAffected if CRIU creates files in directories that allow unprivileged users to create or replace files (such as sticky-bit not set tmp directories)
A system is affected if CRIU is installed, the daemon is active, and log/dump files are created with insecure permissions or in unsafe directory paths accessible to unprivileged users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict file creation permissions and validate directory paths when the CRIU daemon creates log and dump files; ensure files are created with appropriate ownership and restricted permissions.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5228 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5228 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data