Home / CVE DB / CVE-2018-6556
Standard
Vulnerability Identifier

CVE-2018-6556

2018-08-10
Severity Assessment
LOW
CVSS v3.x Score
Clinical Analysis (Description)

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.

Vector Sequencing

Attack Parameters

Impact Consequences

Technical Impact

CVSS v2 Score (Legacy)
2.1

For backward compatibility

EPSS Probability
0.06%

Percentile: 18.4%

Weakness Classification

CWE-CWE-417

Affected Population

Affected Configurations

Total: 18 detected entries

Software List Scrollable
su
caas_platform
Vendor: suse • v1.0
ca
ubuntu_linux
Vendor: canonical • v18.04
li
lxc
Vendor: linuxcontainers • v2.0.9
li
lxc
Vendor: linuxcontainers • v2.0.3
su
suse_linux_enterprise_server
Vendor: suse • v11
li
lxc
Vendor: linuxcontainers • v3.0.1
li
lxc
Vendor: linuxcontainers • v2.0.2
su
caas_platform
Vendor: suse • v2.0
op
leap
Vendor: opensuse • v15.0
li
lxc
Vendor: linuxcontainers • v2.0.6
li
lxc
Vendor: linuxcontainers • v2.0.7
li
lxc
Vendor: linuxcontainers • v2.0.8
li
lxc
Vendor: linuxcontainers • v2.0.4
li
lxc
Vendor: linuxcontainers • v3.0.0
li
lxc
Vendor: linuxcontainers • v2.0.5
li
lxc
Vendor: linuxcontainers • v2.0.1
li
lxc
Vendor: linuxcontainers • v2.0.0
su
openstack_cloud
Vendor: suse • v6
Timeline

Time Line

PUBLICATION
10 Aug 2018
MODIFICATION
21 Nov 2024
FIRST PATCH
03 Jan 2023
Impact Statistics

Key Metrics

CVSS Score
LOW
Products
18
Affected
Patches
1
Available
Remediation Protocol

Recommended Solution

No automatic solution found. Check vendor references.
Patch Library
Recommended Actions for Administrators

Immediate Action Plan

1. Inventory

Identify all affected systems in your infrastructure.

2. Assessment

Assess exposure and criticality for your organization.

3. Mitigation

Apply patches or available workarounds.

4. Verification

Test and confirm effectiveness of applied measures.