# CVE-2017-6507: Security feature bypass in n/a

> Attackers can bypass AppArmor confinement for processes using non-standard profile locations, increasing the attack surface of intended confined applications.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-6507, GHSA-44p8-9hqx-3rqg, SUSE-SU-2017:1151-1, UBUNTU-CVE-2017-6507, USN-3247-1, openSUSE-SU-2024:10627-1

## What is CVE-2017-6507?

CVE-2017-6507 is a medium-severity vulnerability in n/a, published on 24 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in AppArmor before 2.12. Incorrect handling of unknown AppArmor profiles in AppArmor init scripts, upstart jobs, and/or systemd unit files allows an attacker to possibly have increased attack surfaces of processes that were intended to be confined by AppArmor. This is due to the common logic to handle 'restart' operations removing AppArmor profiles that aren't found in the typical filesystem locations, such as /etc/apparmor.d/. Userspace projects that manage their own AppArmor profiles in atypical directories, such as what's done by LXD and Docker, are affected by this flaw in the AppArmor init script logic.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-6507?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apparmor` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 2.8.2-54.1 |
| `apparmor` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 2.8.2-54.1 |
| `apparmor` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 2.8.2-54.1 |
| `apparmor` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 2.8.2-54.1 |
| `apparmor` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 2.8.2-54.1 |
| `apparmor` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 2.8.2-54.1 |
| `apparmor` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2.8.2-54.1 |
| `apparmor` | SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 2.8.2-54.1 |
| `apparmor` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 2.8.2-54.1 |

Products: Apparmor Apparmor, Canonical Ubuntu Core, Canonical Ubuntu Touch.

## How do I fix CVE-2017-6507?

Upgrade to a fixed version.

## Is CVE-2017-6507 being exploited?

There is no known exploitation of CVE-2017-6507 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6507 and fix it if it is affected.

What it is: CVE-2017-6507 is a medium-severity vulnerability in n/a, published on 24 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6507 in the wild and no public exploit code.

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-2017-6507/ (Markdown: https://insights.sbomify.com/CVE-2017-6507/index.md)
```

## Sources

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

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