CVE-2017-6507
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data tampering.
- Exploit odds
- 1.6% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.6% in the next 30 days (EPSS).
- Severity: 5.9 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.6% · EPSS, next 30 days
- Weakness
- CWE-269 · Improper privilege management
- Record status
- Modified
Affected
- Apparmor ≤ 2.11
- Canonical Ubuntu Core 15.04
- Canonical Ubuntu Touch 15.04
Attack profile CVSS 3.0 · 5.9
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-6507.md and follow it. Check whether this project is affected by CVE-2017-6507. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- 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
- 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
References
- 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
- 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