CVE-2018-6556: The lxc-user-nic component of LXC allows unprivileged users to open arbitrary files
Noroxi assessment
Priority: Monitor (action score 13/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.35% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: n/a LXC 3.0.2.
Low priority for now. Upgrade to n/a LXC 3.0.2 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-user-nic when asked to delete a network interface will unconditionally open a user provided path. This code path may be used by an unprivileged user to check for the existence of a path which they wouldn't otherwise be able to reach. It may also be used to trigger side effects by causing a (read-only) open of special kernel files (ptmx, proc, sys). Affected releases are LXC: 2.0 versions above and including 2.0.9; 3.0 versions above and including 3.0.0, prior to 3.0.2.
- Published
- Aug 10, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-417
Report tools
Action score
13
Low priority for now.
- CVSS
- 13 / 40 · 3.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| linuxcontainers | lxc | cpe:2.3:a:linuxcontainers:lxc |
| suse | caas platform | cpe:2.3:a:suse:caas_platform |
| suse | openstack cloud | cpe:2.3:a:suse:openstack_cloud |
| suse | suse linux enterprise server | cpe:2.3:o:suse:suse_linux_enterprise_server |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (canonical). Independent of NVD's CPE analysis and usually ahead of it.
n/a LXC
- 2.0.9 and later · before 2.0*affected
- 3.0.0 and later · before 3.0*affectedfixed in 3.0.2
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux18.04
- linuxcontainers lxc2.0.0 and later · up to 2.0.9 inclusive
- linuxcontainers lxc3.0.0 and later · before 3.0.2
- opensuse leap15.0
- suse caas platform1.0
- suse caas platform2.0
- suse openstack cloud6
- suse suse linux enterprise server11
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | lxc | from 2.0.0 · before 2.1.1-r9 | 2.1.1-r9 |
| Alpine:v3.6 | lxc | from 2.0.0 · before 2.0.9-r1 | 2.0.9-r1 |
| Alpine:v3.7 | lxc | from 2.0.0 · before 2.1.1-r3 | 2.1.1-r3 |
| Debian:12 | lxc | before 1:2.0.9-6.1 | 1:2.0.9-6.1 |
| openSUSE:Leap 15.0 | lxc | before 3.1.0-lp150.2.10.1 | 3.1.0-lp150.2.10.1 |
| openSUSE:Leap 15.0 | lxcfs | before 3.0.3-lp150.2.3.1 | 3.0.3-lp150.2.3.1 |
| openSUSE:Tumbleweed | lxc | before 4.0.9-1.1 | 4.0.9-1.1 |
| SUSE:Package Hub 15 | lxc | before 2.0.9-bp150.5.6.1 | 2.0.9-bp150.5.6.1 |
| SUSE:Package Hub 15 | lxc | before 3.1.0-bp150.5.3.1 | 3.1.0-bp150.5.3.1 |
| SUSE:Package Hub 15 | lxcfs | before 3.0.3-bp150.3.3.1 | 3.0.3-bp150.3.3.1 |
Same product
canonical: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3493The overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities…KEV76This week
- CVE-2017-14492Heap-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a denial of service (crash) or execute arbitrary code…67This week
- CVE-2017-14493Stack-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a denial of service (crash) or execute arbitrary code…65This week
Published before and after this one in the same product
- ← EarlierCVE-2016-9597Jul 30, 2018 · It was found that Red Hat JBoss Core Services erratum RHSA-2016:2957 for CVE-2016-3705 did not actually include the fix for the issue found…31Monitor
- ← EarlierCVE-2018-14526Aug 8, 2018 · An issue was discovered in rsn_supp/wpa.c in wpa_supplicant 2.0 through 2.6.26Monitor
- Later →CVE-2018-0501Aug 20, 2018 · The mirror:// method implementation in Advanced Package Tool (APT) 1.6.x before 1.6.4 and 1.7.x before 1.7.0~alpha3 mishandles gpg…23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| n/a LXC | 3.0.2 | Vendor (CNA) |
| alpine:lxc | 2.1.1-r9 · Alpine:v3.10 | Package registry (OSV) |
| debian:lxc | 1:2.0.9-6.1 · Debian:12 | Package registry (OSV) |
| opensuse:lxc | 3.1.0-lp150.2.10.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| opensuse:lxcfs | 3.0.3-lp150.2.3.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| suse:lxc | 3.1.0-bp150.5.3.1 · SUSE:Package Hub 15 | Package registry (OSV) |
| suse:lxcfs | 3.0.3-bp150.3.3.1 · SUSE:Package Hub 15 | Package 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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-417 · Communication Channel ErrorsCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- lists.opensuse.org/opensuse-security-announce/2019-04/msg00076.html
- lists.opensuse.org/opensuse-security-announce/2019-04/msg00091.html
- lists.opensuse.org/opensuse-security-announce/2019-05/msg00073.html
- bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591
- bugzilla.suse.com/show_bug.cgi?id=988348
- security.gentoo.org/glsa/201808-02
- usn.ubuntu.com/usn/usn-3730-1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.