Local root escalation via predictable coredump symlink
Published Dec 7, 2015 · Updated Aug 27, 2026
Symlink handling in ABRT before 2.7.1 allows local users with write access to an ABRT problem directory to gain root privileges. In abrt-hook-ccpp, xopen3 opens a predictable basename-coredump path with O_TRUNC and follows an attacker-planted symlink to its target. Exploitation requires local write access to the dump directory and lets the coredump overwrite a root-controlled file.
Summary
What happened
Symlink handling in ABRT before 2.7.1 allows local users with write access to an ABRT problem directory to gain root privileges. In abrt-hook-ccpp, xopen3 opens a predictable basename-coredump path with O_TRUNC and follows an attacker-planted symlink to its target. Exploitation requires local write access to the dump directory and lets the coredump overwrite a root-controlled file.
The record
- CVE
- CVE-2015-5287
- Published
- Dec 7, 2015
- Updated
- Aug 27, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 7, 2015CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ABRT CentOS 7.1 and Fedora 22 local privilege escalationfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo