Skip to content
Fencer Intel
high 7.2

CVE-2015-1335 json

lxc-start in lxc before 1.0.8 and 1.1.x before 1.1.4 allows local container administrators to escape AppArmor confinement via a symlink att…

published 2015-10-01 11 y ago modified 2026-06-17 4 mo ago also EUVD-2015-1475

cvss
7.2
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

lxc-start in lxc before 1.0.8 and 1.1.x before 1.1.4 allows local container administrators to escape AppArmor confinement via a symlink attack on a (1) mount target or (2) bind mount source.

Patch / fix

  • lxc Debian 14, Debian 13, Debian 12 1:1.0.8-1

debian advisories DEBIAN-CVE-2015-1335

  • lxc Ubuntu 14.04 LTS 1.0.7-0ubuntu0.5

ubuntu advisories UBUNTU-CVE-2015-1335

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • lxc SLES for SAP 11 SP4, SLES for SAP 11 SP3, SLES 11 SP4 +6 more 0.8.0-0.25.1

suse advisories SUSE-SU-2015:1829-1

  • lxc openSUSE Tumbleweed 2.0.4-2.1

opensuse advisories openSUSE-SU-2024:10416-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-1335 updated cvss 3.5

lxc: Directory traversal flaw when lxc-start is initially setting up the mounts for a container

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.