Search for packages
| purl | pkg:deb/debian/lxc@1:3.1.0%2Breally3.0.3-8 |
| Next non-vulnerable version | 1:4.0.6-2+deb11u2 |
| Latest non-vulnerable version | 1:4.0.6-2+deb11u2 |
| Risk | 1.6 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-xq22-fmtf-8yhs
Aliases: CVE-2022-47952 |
lxc-user-nic in lxc through 5.0.1 is installed setuid root, and may allow local users to infer whether any file exists, even within a protected directory tree, because "Failed to open" often indicates that a file does not exist, whereas "does not refer to a network namespace path" often indicates that a file exists. NOTE: this is different from CVE-2018-6556 because the CVE-2018-6556 fix design was based on the premise that "we will report back to the user that the open() failed but the user has no way of knowing why it failed"; however, in many realistic cases, there are no plausible reasons for failing except that the file does not exist. |
Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-1rds-zc87-auf6 | A vulnerability has been found in LXC which may allow for arbitrary file access (read-only). |
CVE-2018-6556
|
| VCID-7juj-78y7-g7b6 | Containment Errors (Container Errors) runc allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to `/proc/self/exe`. |
CVE-2019-5736
|
| VCID-xx5x-hgur-xbbj | In LXC 2.0, many template scripts download code over cleartext HTTP, and omit a digital-signature check, before running it to bootstrap containers. |
CVE-2017-18641
|