CVE-2017-6507

medium

Published 2017-03-24 · Modified 2026-05-13

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

5.9

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

CVSS v4 NEW

—

not yet in upstream

VIR risk

5.9

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.

Predictions

Exploit likelihood

69%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

OS	Version	Status	Fixed in
debian	bookworm	fixed	`2.11.0-3`
debian	bullseye	fixed	`2.11.0-3`
debian	forky	fixed	`2.11.0-3`
debian	sid	fixed	`2.11.0-3`
debian	trixie	fixed	`2.11.0-3`
sles		affected

Application impact

Vendor	Product	Versions	Fixed
apparmor	apparmor	`{"endIncluding":"2.11"}`

References

CWEs

CWE-269

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.