Skip to content
Noroxi
NVD / CVE Program· CNA canonical

CVE-2015-1335: 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…

HighCVSS 7.2 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
  • No special conditions are required; it is repeatable.
  • Fixed version: lxc (Debian:12) 1:1.0.8-1; lxc (Debian:6.0) 0.7.2-1+deb6u1; lxc (Debian:8) 1:1.0.6-6+deb8u2.

Low priority for now. Upgrade to lxc (Debian:12) 1:1.0.8-1; lxc (Debian:6.0) 0.7.2-1+deb6u1; lxc (Debian:8) 1:1.0.6-6+deb8u2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Oct 1, 2015
Updated
Jun 16, 2026
EPSS
0.4% · 40th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2015-1335

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxcontainerslxc
canonicalubuntu linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux14.04
  • canonical ubuntu linux15.04
  • linuxcontainers lxcup to 1.0.7 inclusive
  • linuxcontainers lxc1.1.0
  • linuxcontainers lxc1.1.1
  • linuxcontainers lxc1.1.2
  • linuxcontainers lxc1.1.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12lxcbefore 1:1.0.8-11:1.0.8-1
Debian:6.0lxcbefore 0.7.2-1+deb6u10.7.2-1+deb6u1
Debian:8lxcbefore 1:1.0.6-6+deb8u21:1.0.6-6+deb8u2
openSUSE:Tumbleweedlxcbefore 2.0.4-2.12.0.4-2.1
SUSE:Linux Enterprise Software Development Kit 11 SP3lxcbefore 0.8.0-0.25.10.8.0-0.25.1

Other highest-scoring records for the same primary product.

  • CVE-2016-8649lxc-attach in LXC before 1.0.9 and 2.x before 2.0.6 allows an attacker inside of an unprivileged container to use an inherited file…
    37Monitor
  • CVE-2016-10124An issue was discovered in Linux Containers (LXC) before 2016-02-22.
    34Monitor
  • CVE-2017-18641In LXC 2.0, many template scripts download code over cleartext HTTP, and omit a digital-signature check, before running it to bootstrap…
    32Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2015-1331Aug 12, 2015 · lxclock.c in LXC 1.1.2 and earlier allows local users to create arbitrary files via a symlink attack on /run/lock/lxc/*.
    19Monitor
  • ← EarlierCVE-2015-1334Aug 12, 2015 · attach.c in LXC 1.1.2 and earlier uses the proc filesystem in a container, which allows local container users to escape AppArmor or SELinux…
    18Monitor
  • Later →CVE-2017-5985Mar 14, 2017 · lxc-user-nic in Linux Containers (LXC) allows local users with a lxc-usernet allocation to create network interfaces on the host and choose…
    13Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:lxc1:1.0.8-1 · Debian:12Package registry (OSV)
opensuse:lxc2.0.4-2.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:lxc0.8.0-0.25.1 · SUSE:Linux Enterprise Software Development Kit 11 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
C · data can be read
Integrity
C · data or configuration can be modified
Availability
C · the service can be disrupted
Attack complexity
Low
Confidentiality impact
C
Integrity impact
C
Availability impact
C

CVSS vector

AV:L/AC:L/Au:N/C:C/I:C/A:C

nvd-primary

References

All records