An issue was discovered in AppArmor before 2.12. Incorrect handling...
Vulnerability 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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2017-6507
Credits & Attribution
No credits recorded in the NVD database.
References
- http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648
- http://www.securityfocus.com/bid/97223
- https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6507.html
- https://bugs.launchpad.net/apparmor/+bug/1668892
- http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647
Affected Vendor
apparmor
View all reports →Affected Software
Timeline
CVSS Vectors
Weaknesses (CWE)
No CWE data available
MITRE ATT&CK TTPs
No associated TTPs found for this vulnerability.