CVE-2015-5287
Redhat Automatic Bug Reporting Tool ≤ 2.7.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2015-5287 is a high-severity Link Following (CWE-59) vulnerability in Redhat Automatic Bug Reporting Tool. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Escape to Host (T1611); ranked in the top 8% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2015-5264
Vulnerability Data
The abrt-hook-ccpp help program in Automatic Bug Reporting Tool (ABRT) before 2.7.1 allows local users with certain permissions to gain privileges via a symlink attack on a file with a predictable name, as demonstrated by /var/tmp/abrt/abrt-hax-coredump or /var/spool/abrt/abrt-hax-coredump.
- CWE(s)
- KEV Date Added
- 26 August 2026
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly require code to validate paths and avoid unsafe link following.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect link-following flaws before release.
Training developers about secure file handling practices (checking for symlinks, using safe file APIs, avoiding predictable temp filenames) reduces some instances of link-following defects, but the effect is a minority one because the practice is fallible and the stronger control is A.8.29 security testing, consistent with the A.8.28 -> CWE-79 and A.6.3 -> CWE-598 anchors.
Secure coding standards directly address canonicalization and symlink attacks during implementation.
A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-59 is an ordinary implementation defect, but the clause's reach is bounded by the supplier's fallible practice and the ceiling on this verb is `partial`.
A.8.8's reach is DISCLOSURE — it surfaces link-following flaws only where they appear as published advisories in third-party components in the inventory. CWE-59 does surface as CVEs (many observed examples), so the disclosed share is non-trivial, but most link-following instances live in first-party code or in third-party components without a published advisory, which A.8.8 does not reach.