Information Exposure Affecting lxc package, versions <1:5.0.2-1


Severity

Recommended
0.0
low
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.72% (53rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-LXC-20158730
  • published27 Sept 2026
  • disclosed1 Jan 2023

Introduced: 1 Jan 2023

CVE-2022-47952  (opens in a new tab)
CWE-203  (opens in a new tab)

How to fix?

Upgrade Echo:latest lxc to version 1:5.0.2-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream lxc package and not the lxc package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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 Base Scores

version 3.1