Advisory

UBUNTU-CVE-2017-6507

Also known as: CVE-2017-6507

Summary

The record has no summary.

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.

Severity

Medium Basis: CVSS v3 score 5.9, vector CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Dates

Published
2017-03-24 00:00 UTC
Modified
2026-04-22 11:29 UTC

Affected packages and fixes

apparmor

Debian packages (deb) · Ubuntu 14.04

Affected

  • introduced 0, fixed 2.10.95-0ubuntu2.6~14.04.1 (ecosystem)

Fixed versions

2.10.95-0ubuntu2.6~14.04.1

Fix

  • Fixed version 2.10.95-0ubuntu2.6~14.04.1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

apparmor

Debian packages (deb) · Ubuntu 16.04

Affected

  • introduced 0, fixed 2.10.95-0ubuntu2.6 (ecosystem)

Fixed versions

2.10.95-0ubuntu2.6

Fix

  • Fixed version 2.10.95-0ubuntu2.6
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Ubuntu Security Notices · CC BY-SA 4.0

Sources & licences