The Quarterly Threat Landscape Report is out. See what attackers are targeting now.Read report
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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade apparmor | Jul 30, 2024 | Mar 24, 2017 |
| Suse | — | Upgrade apparmor-parser-langUpgrade apparmor-utilsUpgrade apparmor-utils-langUpgrade python3-apparmorUpgrade libapparmor-develUpgrade pam_apparmorUpgrade libapparmor1Upgrade perl-apparmorUpgrade sles12sp1-docker-imageUpgrade apparmor-abstractionsUpgrade apparmor-profilesUpgrade sles12-docker-imageUpgrade apparmor-parserUpgrade sles12sp2-docker-imageUpgrade libapparmor1-32bitUpgrade pam_apparmor-32bitUpgrade apparmor-docsUpgrade apache2-mod_apparmor | Apr 10, 2017 | Mar 24, 2017 |
| Ubuntu | — | Upgrade apparmor | Mar 29, 2017 | Mar 24, 2017 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub