CVE-2022-47952
published 2023-01-01CVE-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…
PriorityP411low3.3CVSS 3.1
AVLACLPRLUINSUCLINAN
EPSS
0.72%
53.4th percentile
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
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | lxc | < lxc 1:5.0.2-1 (bookworm) | lxc 1:5.0.2-1 (bookworm) |
| linuxcontainers | lxc | <= 5.0.1 | — |
| linuxcontainers | lxc | >= 0 < 1:4.0.6-2+deb11u2 | 1:4.0.6-2+deb11u2 |
| linuxcontainers | lxc | >= 0 < 1:5.0.2-1 | 1:5.0.2-1 |
| linuxcontainers | lxc | >= 0 < 1:5.0.2-1 | 1:5.0.2-1 |
| linuxcontainers | lxc | >= 0 < 1:5.0.2-1 | 1:5.0.2-1 |
| ubuntu | lxc | — | — |
CVSS provenance
nvdv3.13.3LOWCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
osv3.3LOW
vendor_debian3.3LOW
vendor_ubuntu3.3LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
LXC vulnerabilities
vendor_ubuntu·2026-09-28·CVSS 3.3
CVE-2022-47952 [LOW] LXC vulnerabilities
Title: LXC vulnerabilities
Summary: Several security issues were fixed in LXC.
Maher Azzouzi discovered that LXC did not correctly handle logging
certain failure messages. An attacker could possibly use this issue
to leak sensitive information. This issue only affected
Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, Ubuntu 20.04 LTS,
Ubuntu 22.04 LTS and Ubuntu 24.04 LTS. (CVE-2022-47952)
Sam Sanoop discovered that LXC did not correctly handle certain forms
of user authorization. An attacker could possibly use this issue to
cause a denial of service. (CVE-2026-39402)
Instructions: After a standard system update you need to restart LXC containers to
make all the necessary changes.
Debian
CVE-2022-47952: lxc - lxc-user-nic in lxc through 5.0.1 is installed setuid root, and may allow local ...
vendor_debian·2022·CVSS 3.3
CVE-2022-47952 [LOW] CVE-2022-47952: lxc - lxc-user-nic in lxc through 5.0.1 is installed setuid root, and may allow local ...
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.
Scope: local
bookworm: resolved (fixed in 1:5.0.2-1)
bullseye: resolved (fixed in 1:4.0.6-2+deb11u2)
forky: resolved (fixed in 1:5.0.2-1)
sid: resolved
GHSA
GHSA-qv29-rjwj-jjrm: lxc-user-nic in lxc through 5
ghsa_unreviewed·2023-01-01·CVSS 3.3
CVE-2022-47952 [LOW] CWE-203 GHSA-qv29-rjwj-jjrm: lxc-user-nic in lxc through 5
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.
OSV
CVE-2022-47952: lxc-user-nic in lxc through 5
osv·2023-01-01·CVSS 3.3
CVE-2022-47952 [LOW] CVE-2022-47952: lxc-user-nic in lxc through 5
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/comments/45https://github.com/MaherAzzouzi/CVE-2022-47952https://github.com/lxc/lxc/blob/0b83d71c2c8f3bac9503f894cd84584f79258bb3/lxc.spec.in#L274https://github.com/lxc/lxc/blob/0b83d71c2c8f3bac9503f894cd84584f79258bb3/src/lxc/cmd/lxc_user_nic.c#L1085-L1104https://lists.debian.org/debian-lts-announce/2023/08/msg00025.htmlhttps://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/comments/45https://github.com/MaherAzzouzi/CVE-2022-47952https://github.com/lxc/lxc/blob/0b83d71c2c8f3bac9503f894cd84584f79258bb3/lxc.spec.in#L274https://github.com/lxc/lxc/blob/0b83d71c2c8f3bac9503f894cd84584f79258bb3/src/lxc/cmd/lxc_user_nic.c#L1085-L1104https://lists.debian.org/debian-lts-announce/2023/08/msg00025.html
2023-01-01
Published