CVE-2017-6507
Last modified
CVE-2017-6507 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.59% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apparmor | Apparmor | <= 2.11 |
| Canonical | Ubuntu Core | 15.04 |
| Canonical | Ubuntu Touch | 15.04 |
References
- http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647Issue Tracking, Patch, Third Party Advisory
- http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648Issue Tracking, Patch, Third Party Advisory
- https://bugs.launchpad.net/apparmor/+bug/1668892Issue Tracking, Patch, Third Party Advisory
- https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6507.htmlThird Party Advisory
- http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647Issue Tracking, Patch, Third Party Advisory
- http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648Issue Tracking, Patch, Third Party Advisory
- https://bugs.launchpad.net/apparmor/+bug/1668892Issue Tracking, Patch, Third Party Advisory
- https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6507.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-6507?
How severe is CVE-2017-6507?
How do I fix CVE-2017-6507?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-6501An issue was discovered in ImageMagick 6.9.7. A specially cr…
- CVE-2017-6502An issue was discovered in ImageMagick 6.9.7. A specially cr…
- CVE-2017-6503WebUI in qBittorrent before 3.3.11 did not escape many value…
- CVE-2017-6504WebUI in qBittorrent before 3.3.11 did not set the X-Frame-O…
- CVE-2017-6505The ohci_service_ed_list function in hw/usb/hcd-ohci.c in QE…6.5
- CVE-2017-6506In Azure Data Expert Ultimate 2.2.16, the SMTP verification …
- CVE-2017-6508CRLF injection vulnerability in the url_parse function in ur…
- CVE-2017-6509Smith0r/burgundy-cms before 2017-03-06 is vulnerable to a re…
- CVE-2017-6510Easy File Sharing FTP Server version 3.6 is vulnerable to a …
- CVE-2017-6511andrzuk/FineCMS before 2017-03-06 is vulnerable to a reflect…6.1
- CVE-2017-6512Race condition in the rmtree and remove_tree functions in th…5.9
- CVE-2017-6513The WHMCS Reseller Module V2 2.0.2 in Softaculous Virtualizo…
Are you affected by CVE-2017-6507?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
