dbcve.org
Ubuntu Core LauncherApplication · Canonical

CVE-2016-1580

CRITICAL · 9.8 CVSS v3.0 Published 2016-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The setup_snappy_os_mounts function in the ubuntu-core-launcher package before 1.0.27.1 improperly determines the mount point of bind mounts when using snaps, which might allow remote attackers to obtain sensitive information or gain privileges via a snap with a name starting with "ubuntu-core."

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 · high confidence

The setup_snappy_os_mounts function in ubuntu-core-launcher before version 1.0.27.1 incorrectly determines mount points for bind mounts when processing snaps, allowing a snap with a name starting with 'ubuntu-core' to potentially access or manipulate files outside its intended namespace, leading to information disclosure or privilege escalation.

MitigationUpgrade ubuntu-core-launcher to version 1.0.27.1 or later to patch the improper mount point determination logic in the setup_snappy_os_mounts function.

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
Ubuntu Core LauncherApplication
Affected:= 1.0.27

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.0/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 ubuntu-core-launcher version
    Run 'dpkg -l ubuntu-core-launcher' or check the installed package version using your system's package manager to retrieve the exact version number.
    Affected if The installed version is 1.0.27 exactly, which is the affected version prior to the 1.0.27.1 patch.
  2. Confirm the patch version is absent
    Compare your installed version against the fixed version 1.0.27.1. If your version is 1.0.27 or lower without the 1.0.27.1 patch applied, the vulnerability is present.
    Affected if The version is 1.0.27 without the 1.0.27.1 security patch applied.
  3. Enumerate installed snaps with names starting with ubuntu-core
    Run 'snap list' or check the snap metadata directory (typically /snap or /var/lib/snapd/snaps) for snap packages whose names begin with the string 'ubuntu-core'.
    Affected if A snap with a name starting with 'ubuntu-core' is installed on the system.
  4. Verify bind mount configuration for affected snaps
    Inspect the system's active mount table using 'mount' or check /proc/self/mountinfo to see if any bind mounts created by ubuntu-core-launcher for snaps with names starting with 'ubuntu-core' exist outside the expected snap namespace directory.
    Affected if Bind mounts for snaps with 'ubuntu-core' prefix are present outside the intended /snap or /var/lib/snapd namespace boundaries.

You are affected if ubuntu-core-launcher version 1.0.27 is installed without the 1.0.27.1 patch AND a snap with a name starting with 'ubuntu-core' exists on the system, allowing improper bind mount paths that escape the snap's namespace.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ubuntu-core-launcher to version 1.0.27.1 or later to patch the improper mount point determination logic in the setup_snappy_os_mounts function.

Recommended fix High confidence

ubuntu-core-launcher >= 1.0.27.1

  1. Update package repository lists: sudo apt-get update
  2. Upgrade the ubuntu-core-launcher package to version 1.0.27.1 or later: sudo apt-get install ubuntu-core-launcher
  3. Verify the installed version matches or exceeds 1.0.27.1: dpkg -l ubuntu-core-launcher

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

Fix this in Ubuntu Core Launcher Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1580 — 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-1580 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