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.

Published: 2023-01-01 Last update: 2025-04-10 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-47952 is rated Moderate Risk (42.8/100): CVSS Low severity, with medium exploitation likelihood (EPSS 2.32%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-47952

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 2.46% 2.32% -0.14%
2 2026-05-04 2.32% 2.46% +0.15%
3 2026-04-24 — 2.32% —

Full EPSS history (26 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-47952

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 1.4 [email protected]
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-47952

OS Trackers for CVE-2022-47952

vendor priority summary link
alpine low CVE-2022-47952: 1 source package rows (lxc); 17 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 10. https://security.alpinelinux.org/vuln/CVE-2022-47952
debian not yet assigned CVE-2022-47952 not yet assigned priority: Debian including 1 source packages (lxc), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-47952
suse medium CVE-2022-47952 severity moderate: SUSE including 22 source package names (liblxc-devel-5.0.2-1.1, liblxc-devel-6.0.2-bp155.4.3.1, …), 36 product×package rows across 6 product lines (SUSE Linux Enterprise Server 11 SP3 for Teradata, SUSE Package Hub 15 SP5, … (6 product lines)): Fixed 35, Known Not Affected 1. https://www.suse.com/security/cve/CVE-2022-47952/
ubuntu low CVE-2022-47952 low priority: Ubuntu including 1 source packages (lxc), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needed 6, ignored 3, not-affected 3, released 1. https://ubuntu.com/security/CVE-2022-47952

Affected software / configurations for CVE-2022-47952

Vendor Product Version Raw CPE
linuxcontainers lxc <= 5.0.1 cpe:2.3:a:linuxcontainers:lxc:*:*:*:*:*:*:*:*

References for CVE-2022-47952

cvelogic Threat Intelligence