CVE-2015-1318 is a privilege escalation vulnerability in Apport (versions 2.13 through 2.17.x before 2.17.1), Ubuntu's crash reporting tool. The vulnerability arises from unsafe handling of core dumps and improper use of chroot and namespace features, particularly when Apport is triggered via a crafted /usr/share/apport/apport file in a container or namespace. Attackers can exploit race conditions, symlink attacks, and trust in attacker-controlled paths to escalate privileges to root or take ownership of arbitrary files. The vulnerability is especially severe in containerized environments and is exploitable by local users with user namespace capabilities.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit module (Ruby file) that exploits a local privilege escalation vulnerability in the Apport (Ubuntu) and ABRT (Fedora) coredump handlers (CVE-2015-1318). The exploit targets systems where the coredump handler is configured to chroot and execute either /usr/share/apport/apport or /usr/libexec/abrt-hook-ccpp, and where unprivileged user namespaces are enabled. The module checks for the presence of a vulnerable configuration by reading /proc/sys/kernel/core_pattern and verifying the Apport or ABRT version. If the system is vulnerable, the module uploads a precompiled exploit binary and a custom payload (generated by Metasploit), executes the exploit to gain root privileges, and runs the payload as root. The exploit is operational and provides root access on affected systems. The structure is typical for a Metasploit local exploit module, with clear separation of initialization, vulnerability checking, and exploitation logic. The only file present is the exploit module itself.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.