{"api_version":"1","generated_at":"2026-04-23T06:18:32+00:00","cve":"CVE-2017-6507","urls":{"html":"https://cve.report/CVE-2017-6507","api":"https://cve.report/api/cve/CVE-2017-6507.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2017-6507","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2017-6507"},"summary":{"title":"CVE-2017-6507","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.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2017-03-24 07:59:00","updated_at":"2019-10-03 00:03:00"},"problem_types":["CWE-269"],"metrics":[],"references":[{"url":"http://www.securityfocus.com/bid/97223","name":"97223","refsource":"BID","tags":[],"title":"Ubuntu AppArmor CVE-2017-6507 Security Bypass Vulnerability","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647","name":"http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647","refsource":"CONFIRM","tags":["Issue Tracking","Patch","Third Party Advisory"],"title":"~apparmor-dev/apparmor/master : revision 3647","mime":"text/xml","httpstatus":"200","archivestatus":"200"},{"url":"https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6507.html","name":"https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6507.html","refsource":"CONFIRM","tags":["Third Party Advisory"],"title":"CVE-2017-6507 in Ubuntu","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648","name":"http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648","refsource":"CONFIRM","tags":["Issue Tracking","Patch","Third Party Advisory"],"title":"~apparmor-dev/apparmor/master : revision 3648","mime":"text/xml","httpstatus":"200","archivestatus":"200"},{"url":"https://bugs.launchpad.net/apparmor/+bug/1668892","name":"https://bugs.launchpad.net/apparmor/+bug/1668892","refsource":"CONFIRM","tags":["Issue Tracking","Patch","Third Party Advisory"],"title":"Bug #1668892 “CVE-2017-6507: apparmor service restarts and packa...” : Bugs : AppArmor","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-6507","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-6507","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2017","cve_id":"6507","vulnerable":"1","versionEndIncluding":"2.11","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"apparmor","cpe5":"apparmor","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2017","cve_id":"6507","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"canonical","cpe5":"ubuntu_core","cpe6":"15.04","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2017","cve_id":"6507","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"canonical","cpe5":"ubuntu_core","cpe6":"15.04","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2017","cve_id":"6507","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"canonical","cpe5":"ubuntu_touch","cpe6":"15.04","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2017","cve_id":"6507","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"canonical","cpe5":"ubuntu_touch","cpe6":"15.04","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2017-6507","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"name":"http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648","refsource":"CONFIRM","url":"http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3648"},{"name":"97223","refsource":"BID","url":"http://www.securityfocus.com/bid/97223"},{"name":"https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6507.html","refsource":"CONFIRM","url":"https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-6507.html"},{"name":"https://bugs.launchpad.net/apparmor/+bug/1668892","refsource":"CONFIRM","url":"https://bugs.launchpad.net/apparmor/+bug/1668892"},{"name":"http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647","refsource":"CONFIRM","url":"http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3647"}]}},"nvd":{"publishedDate":"2017-03-24 07:59:00","lastModifiedDate":"2019-10-03 00:03:00","problem_types":["CWE-269"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.0","vectorString":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"NONE","baseScore":5.9,"baseSeverity":"MEDIUM"},"exploitabilityScore":2.2,"impactScore":3.6},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:M/Au:N/C:N/I:P/A:N","accessVector":"NETWORK","accessComplexity":"MEDIUM","authentication":"NONE","confidentialityImpact":"NONE","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":4.3},"severity":"MEDIUM","exploitabilityScore":8.6,"impactScore":2.9,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:apparmor:apparmor:*:*:*:*:*:*:*:*","versionEndIncluding":"2.11","cpe_name":[]}]},{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:o:canonical:ubuntu_touch:15.04:*:*:*:*:*:*:*","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:o:canonical:ubuntu_core:15.04:*:*:*:*:*:*:*","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2017","CveId":"6507","Ordinal":"103193","Title":"CVE-2017-6507","CVE":"CVE-2017-6507","Year":"2017"},"notes":[{"CveYear":"2017","CveId":"6507","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2017","CveId":"6507","Ordinal":"2","NoteData":"2017-03-24","Type":"Other","Title":"Published"},{"CveYear":"2017","CveId":"6507","Ordinal":"3","NoteData":"2017-03-31","Type":"Other","Title":"Modified"}]}}}