CVE-2015-5287
Red Hat Automatic Bug Reporting Tool (ABRT) contains a privilege escalation vulnerability that could allow local users with certain permissions to gain privileges via a symlink attack on a file with a predictable name. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.
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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- packetstormsecurity.com/files/154592/ABRT-sosreport-Privilege-Escalation.htmlThird Party Advisory
- rhn.redhat.com/errata/RHSA-2015-2505.htmlVendor Advisory
- openwall.com/lists/oss-security/2015/12/01/1Exploit
- oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.htmlThird Party Advisory
- securityfocus.com/bid/78137Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=1266837Exploit
- github.com/abrt/abrt/commit/3c1b60cfa62d39e5fff5a53a5bc53dae189e740ePatch
- exploit-db.com/exploits/38832/Mailing ListThird Party Advisory
- blog.talosintelligence.com/uat-10147-chinese-speaking-adversary-integrates-agentic-ai-into-post-compromise-operations/Third Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2015-5287Third Party AdvisoryUS Government Resource
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 48 days
- CVSS
- 7.8 HIGH
- EPSS (30-day exploit probability)
- 5.0% · top 8% of all CVEs
- Weakness
- CWE-59
- 1.Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.