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.

This update for apparmor provides the following fixes: This security issue was fixed :

  - CVE-2017-6507: Preserve unknown profiles when reloading     apparmor.service (bsc#1029696)

The update package also includes non-security fixes. See advisory for details.

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for apparmor fixes the following issues :

These security issues were fixed :

  - CVE-2017-6507: Preserve unknown profiles when reloading     apparmor.service (lp#1668892, boo#1029696)

  - boo#1017260: Migration to apparmor.service accidentally     disable AppArmor. Note: This will re-enable AppArmor if     it was disabled by the last update. You'll need to     'rcapparmor reload' to actually load the profiles, and     then check aa-status for programs that need to be     restarted to apply the profiles.

These non-security issues were fixed :

  - Fixed crash in aa-logprof on specific change_hat events

  - boo#1016259: Added var.mount dependeny to     apparmor.service

The aa-remove-unknown utility was added to unload unknown profiles (lp#1668892)

The remote Ubuntu 14.04 LTS / 16.04 LTS host has packages installed that are affected by a vulnerability as referenced in the USN-3247-1 advisory.

    Stphane Graber discovered that AppArmor incorrectly unloaded some profiles when restarted or upgraded,     contrary to expected behavior.

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
99978	SUSE SLED12 / SLES12 Security Update : apparmor (SUSE-SU-2017:1151-1)	Nessus	SuSE Local Security Checks	medium
99277	openSUSE Security Update : apparmor (openSUSE-2017-452)	Nessus	SuSE Local Security Checks	medium
99094	Ubuntu 14.04 LTS / 16.04 LTS : AppArmor vulnerability (USN-3247-1)	Nessus	Ubuntu Local Security Checks	medium

Detections

Analytics

CVE-2017-6507

medium

Tenable Plugins

medium

medium

medium