CVE-2017-6507
First published: Fri Mar 24 2017(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/apparmor | 2.13.6-10 3.0.8-3 3.1.7-1 | |
| AppArmor | <=2.11 | |
| Ubuntu Core | =15.04 | |
| Ubuntu Touch | =15.04 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647
- http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648
- http://www.securityfocus.com/bid/97223
- https://bugs.launchpad.net/apparmor/+bug/1668892
- https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6507.html
- https://launchpad.net/bugs/cve/CVE-2017-6507
- https://security-tracker.debian.org/tracker/CVE-2017-6507
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6507
- https://nvd.nist.gov/vuln/detail/CVE-2017-6507
- https://ubuntu.com/security/CVE-2017-6507
Frequently Asked Questions
What is the severity of CVE-2017-6507?
CVE-2017-6507 has been assigned a moderate severity rating due to the potential for increased attack surfaces on confined processes.
How do I fix CVE-2017-6507?
To mitigate CVE-2017-6507, upgrade AppArmor to version 2.13.6-10 or later.
What systems are affected by CVE-2017-6507?
CVE-2017-6507 affects AppArmor versions prior to 2.12, as well as specific releases of Ubuntu Core and Ubuntu Touch.
What is the impact of CVE-2017-6507?
The impact of CVE-2017-6507 could lead to processes intended to be confined by AppArmor being exposed to additional vulnerabilities.
When was CVE-2017-6507 discovered?
CVE-2017-6507 was identified in 2017, affecting the security posture of systems utilizing certain AppArmor configurations.
- agent/type
- agent/last-modified-date
- collector/launchpad-cve
- source/Launchpad
- agent/weakness
- agent/severity
- agent/remedy
- collector/security-tracker-debian
- source/Debian
- agent/software-canonical-lookup
- collector/usn-cve
- source/Ubuntu
- agent/references
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/author
- agent/tags
- agent/softwarecombine
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/debian
- vendor/apparmor
- canonical/apparmor
- version/apparmor/2.11
- vendor/canonical
- canonical/ubuntu core
- version/ubuntu core/15.04
- canonical/ubuntu touch
- version/ubuntu touch/15.04