CVE-2017-6507
Apparmor vulnerability
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
Apparmor, Ubuntu Core, Ubuntu Touch. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Apparmor runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647 · Patch
- bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648 · Patch
- bugs.launchpad.net/apparmor/+bug/1668892 · Patch
- people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6507.html · Third Party Advisory
- www.securityfocus.com/bid/97223
- nvd.nist.gov/vuln/detail/CVE-2017-6507
- cve.org/CVERecord?id=CVE-2017-6507
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.