CVE-2017-6507

See a problem?
Source
https://nvd.nist.gov/vuln/detail/CVE-2017-6507
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2017-6507.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2017-6507
Related
Published
2017-03-24T07:59:00Z
Modified
2024-09-11T02:00:05Z
Severity
  • 5.9 (Medium) CVSS_V3 - CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
Summary
[none]
Details

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.

References

Affected packages

Debian:11 / apparmor

Package

Name
apparmor
Purl
pkg:deb/debian/apparmor?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.11.0-3

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / apparmor

Package

Name
apparmor
Purl
pkg:deb/debian/apparmor?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.11.0-3

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / apparmor

Package

Name
apparmor
Purl
pkg:deb/debian/apparmor?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.11.0-3

Ecosystem specific

{
    "urgency": "not yet assigned"
}