CVE-2016-8649
No known exploitation. EPSS puts it in the 87th percentile. Fixed in 1.0.9.
No public exploit knownFix1.0.9Upgrade to this build
e.g. OID 1.3.6.1.4.1.25623.1.0.842959
What to do
Find your product and version, then upgrade to the build on the right.
- n/a LXC before 1.0.9 and 2.x before 2.0.6Affected: LXC before 1.0.9 and 2.x before 2.0.6Upgrade to: not statedStated by: CVE record
- Linuxcontainers LxcAffected: < 1.0.9Upgrade to: 1.0.9Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
lxc-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 descriptor, of the host's /proc, to access the rest of the host's filesystem via the openat() family of syscalls.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
2.8% chance of exploitation activity in the next 30 days, which ranks it in the 87th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
5 events over 3342 days, from the signal feeds we watch.
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.0 vector
Open in the CVSS calculatorCVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Scored 9.1 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required HighRequires admin or elevated privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
Sources
References in the record
- bugzilla.redhat.com/show_bug.cgi?id=1398242
- bugs.launchpad.net/ubuntu/+source/lxc/+bug/1639345
- github.com/lxc/lxc/commit/81f466d05f2a89cb4f122ef7f593ff3f279b165c
And 3 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Lxc, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI