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 arent found in the typical filesystem locations, such as /etc/apparmor.d/. Userspace projects that manage their own AppArmor profiles in atypical directories, such as whats done by LXD and Docker, are affected by this flaw in the AppArmor init script logic.
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Apparmor | Apparmor | * | 2.11 (including) |
| Apparmor | Ubuntu | devel | * |
| Apparmor | Ubuntu | precise | * |
| Apparmor | Ubuntu | trusty | * |
| Apparmor | Ubuntu | upstream | * |
| Apparmor | Ubuntu | vivid/stable-phone-overlay | * |
| Apparmor | Ubuntu | vivid/ubuntu-core | * |
| Apparmor | Ubuntu | xenial | * |
| Apparmor | Ubuntu | yakkety | * |
| Apparmor | Ubuntu | zesty | * |