SUSE: CVE-2017-6507: SUSE Linux Security Advisory
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.
Solution(s)
- suse-upgrade-apache2-mod_apparmor
- suse-upgrade-apparmor-abstractions
- suse-upgrade-apparmor-docs
- suse-upgrade-apparmor-parser
- suse-upgrade-apparmor-parser-lang
- suse-upgrade-apparmor-profiles
- suse-upgrade-apparmor-utils
- suse-upgrade-apparmor-utils-lang
- suse-upgrade-libapparmor-devel
- suse-upgrade-libapparmor1
- suse-upgrade-libapparmor1-32bit
- suse-upgrade-pam_apparmor
- suse-upgrade-pam_apparmor-32bit
- suse-upgrade-perl-apparmor
- suse-upgrade-python3-apparmor
- suse-upgrade-sles12-docker-image
- suse-upgrade-sles12sp1-docker-image
- suse-upgrade-sles12sp2-docker-image
- Lightweight Endpoint Agent
- Live Dashboards
- Real Risk Prioritization
- IT-Integrated Remediation Projects
- Cloud, Virtual, and Container Assessment
- Integrated Threat Feeds
- Easy-to-Use RESTful API
- Automation-Assisted Patching
- Automated Containment
With Rapid7 live dashboards, I have a clear view of all the assets on my network, which ones can be exploited, and what I need to do in order to reduce the risk in my environment in real-time. No other tool gives us that kind of value and insight.
– Scott Cheney, Manager of Information Security, Sierra View Medical Center