# CVE-2015-1318: Privilege escalation in n/a

> Local attackers can escalate privileges by exploiting a crafted file in the Apport crash reporting system within a container namespace.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Apr 2015
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-cpww-w9jx-qp3p, UBUNTU-CVE-2015-1318, USN-2569-1

## What is CVE-2015-1318?

CVE-2015-1318 is a high-severity vulnerability in n/a, published on 17 Apr 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The crash reporting feature in Apport 2.13 through 2.17.x before 2.17.1 allows local users to gain privileges via a crafted usr/share/apport/apport file in a namespace (container).

Weakness: CWE-264

## Which versions are affected by CVE-2015-1318?

It affects 1 product.


Products: Apport Project Apport.

## How do I fix CVE-2015-1318?

Apply the vendor's patch.

## Is CVE-2015-1318 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1318 exists.

Public exploit code:

- Exploit I used to claim 10% final-grade extra credit in Matthew Might's Compilers class. (github_poc): https://github.com/ScottyBauer/CVE-2015-1318
- Apport / ABRT chroot Privilege Escalation (metasploit)
- Apport/Abrt (Ubuntu / Fedora) - Local Privilege Escalation (exploitdb)
- Apport 2.14.1 (Ubuntu 14.04.2) - Local Privilege Escalation (exploitdb)
- Apport/ABRT - 'chroot' Local Privilege Escalation (Metasploit) (exploitdb)
- Apport/ABRT - 'chroot' Local Privilege Escalation (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2022-28657](https://insights.sbomify.com/CVE-2022-28657/): Denial of service in Apport (high 7.8)
- [CVE-2018-6552](https://insights.sbomify.com/CVE-2018-6552/): Apport treats the container PID as the global PID when /proc/<global_pid>/ is missing (high 7.8)
- [CVE-2017-14177](https://insights.sbomify.com/CVE-2017-14177/): Privilege escalation in Apport (high 7.8)
- [CVE-2017-14179](https://insights.sbomify.com/CVE-2017-14179/): Privilege escalation in Apport (high 7.8)
- [CVE-2017-14180](https://insights.sbomify.com/CVE-2017-14180/): Privilege escalation in Apport (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1318 and fix it if it is affected.

What it is: CVE-2015-1318 is a high-severity vulnerability in n/a, published on 17 Apr 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1318 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-1318/ (Markdown: https://insights.sbomify.com/CVE-2015-1318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-1318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-1318
- OSV: https://osv.dev/vulnerability/CVE-2015-1318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-1318/
Summaries are generated and may contain mistakes; the official description above is the record.