CVE-2017-6507

NameCVE-2017-6507
DescriptionAn 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.
SourceCVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more)
NVD severitymedium (attack range: remote)
Debian Bugs858768

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
apparmor (PTS)jessie2.9.0-3vulnerable
stretch2.11.0-3+deb9u2fixed
buster, sid2.13.1-3fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
apparmorsource(unstable)2.11.0-3medium858768

Notes

[jessie] - apparmor <no-dsa> (Minor issue)
[wheezy] - apparmor <no-dsa> (Experimental/unsupported feature)
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648
https://bugs.launchpad.net/apparmor/+bug/1668892
affects only third-party rules, e.g. from Docker or LXC
LXC in wheezy doesn't support proper isolation

Search for package or bug name: Reporting problems