CVE-2017-6507
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.
Affected products
3- cpe:2.3:o:canonical:ubuntu_core:15.04:*:*:*:*:*:*:*
- cpe:2.3:o:canonical:ubuntu_touch:15.04:*:*:*:*:*:*:*
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
5- bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647nvdIssue TrackingPatchThird Party Advisory
- bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648nvdIssue TrackingPatchThird Party Advisory
- bugs.launchpad.net/apparmor/+bug/1668892nvdIssue TrackingPatchThird Party Advisory
- people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6507.htmlnvdThird Party Advisory
- www.securityfocus.com/bid/97223nvd
News mentions
0No linked articles in our index yet.