Vulnerability record · CVE-2022-47952 · published 1 January 2023
CVE-2022-47952: Linuxcontainers lxc observable discrepancy vulnerability
Linuxcontainers · Lxc
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.
Description
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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/comments/45 | Issue TrackingVendor Advisory |
| https://github.com/MaherAzzouzi/CVE-2022-47952 | Third Party Advisory |
| https://github.com/lxc/lxc/blob/0b83d71c2c8f3bac9503f894cd84584f79258bb3/lxc.spec.in#L274 | Third Party Advisory |
| https://github.com/lxc/lxc/blob/0b83d71c2c8f3bac9503f894cd84584f79258bb3/src/lxc/cmd/lxc_user_nic.c#L1085-L1104 | Third Party Advisory |
| https://lists.debian.org/debian-lts-announce/2023/08/msg00025.html | |
| https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/comments/45 | Issue TrackingVendor Advisory |
| https://github.com/MaherAzzouzi/CVE-2022-47952 | Third Party Advisory |
| https://github.com/lxc/lxc/blob/0b83d71c2c8f3bac9503f894cd84584f79258bb3/lxc.spec.in#L274 | Third Party Advisory |
| https://github.com/lxc/lxc/blob/0b83d71c2c8f3bac9503f894cd84584f79258bb3/src/lxc/cmd/lxc_user_nic.c#L1085-L1104 | Third Party Advisory |
| https://lists.debian.org/debian-lts-announce/2023/08/msg00025.html |
Track CVE-2022-47952 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2022-47952), CISA KEV, FIRST EPSS (scores of 2026-10-05). This page is refreshed as NVD updates the record.