dbcve.org
ApparmorApplication · Canonical

CVE-2016-1585

CRITICAL · 9.8 CVSS v3.1 Published 2019-04-22
Fix available
A fix is available. Upgrade to 2.13.10 / 3.0.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In all versions of AppArmor mount rules are accidentally widened when compiled.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In all versions of AppArmor, mount rules defined in security profiles become unintentionally more permissive when compiled. This policy widening means that allowed mount operations exceed what the profile author intended, potentially allowing attackers to mount paths or filesystems they should not have access to.

MitigationRecompile and redeploy AppArmor profiles after applying the upstream patch. Audit existing mount rules to ensure they reflect the intended restrictive policy, as previously compiled profiles may have been overly permissive.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ApparmorApplication
Affected:< 2.13.10>= 3.0.0, < 3.0.12>= 3.1.0, < 3.1.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed AppArmor version
    Run `apparmor_parser --version` or check your package manager for the apparmor version (e.g., `dpkg -l apparmor` or `rpm -q apparmor`)
    Affected if The version is less than 2.13.10, OR between 3.0.0 and 3.0.12, OR between 3.1.0 and 3.1.6
  2. Locate compiled AppArmor profiles
    Look for compiled profile cache files, typically in /var/lib/apparmor/cache/ or /etc/apparmor.d/disable/ (files with .bin extension or cache directories)
    Affected if Compiled profiles exist in the system
  3. Identify profiles containing mount rules
    Examine your profile source files in /etc/apparmor.d/ for entries beginning with 'mount' keyword, or check compiled profiles with `apparmor_parser -L /var/lib/apparmor/cache/`
    Affected if Any AppArmor profile contains mount rules (e.g., mount, mount_enter, mount_exit)
  4. Confirm profiles were compiled
    Check if the compiled cache in /var/lib/apparmor/cache/ contains profiles that include mount rules, or use `aa-status --compiled` to list compiled profiles
    Affected if Compiled profiles exist AND those profiles include mount rule entries

You are affected if your AppArmor version falls within the vulnerable ranges AND you have compiled profiles that contain mount rules, as the compiled versions may allow more mount operations than the source profiles intended.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.13.10 / 3.0.12 / 3.1.6 or later
Fixed in 2.13.103.0.123.1.6
Interim mitigation

Recompile and redeploy AppArmor profiles after applying the upstream patch. Audit existing mount rules to ensure they reflect the intended restrictive policy, as previously compiled profiles may have been overly permissive.

Recommended fix Moderate confidence

Upgrade to AppArmor 2.13.10 (for 2.x branch), 3.0.12 (for 3.0.x branch), or 3.1.6 (for 3.1.x branch)

  1. Check current AppArmor version with: apparmor_parser --version or aa-status --version
  2. Update your package manager cache: sudo apt-get update (Debian/Ubuntu) or sudo yum check-update (RHEL/CentOS)
  3. Upgrade AppArmor to the fixed release for your branch: sudo apt-get install apparmor (Debian/Ubuntu) or sudo yum update apparmor (RHEL/CentOS)
  4. Verify the installed version matches or exceeds 2.13.10, 3.0.12, or 3.1.6 depending on your branch
  5. Restart AppArmor services if needed: sudo systemctl restart apparmor or sudo service apparmor restart
  6. Review existing AppArmor profiles to ensure they still function correctly after the security fix
Caveat Profiles that were relying on incorrectly widened mount permissions may need adjustment - the fix narrows mount rules back to their intended scope

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apparmor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,496.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1585 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data