ZDF
Sign inSign up

Vulnerabilities

Vulnerability · 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 o

Published Jan 1, 2023 · catalog updated Oct 15, 2026 · lxc-user-nic in lxc through

Check if you run it

No confirmed exploitation is on record for CVE-2022-47952. EPSS is 0.72%. Act only if a listed version of lxc-user-nic in lxc through is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (lxc-user-nic in lxc through).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Low3.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.72%
Remediation
Advisory link
Affected products
Alpine:v3.14 lxc · Alpine:v3.15 lxc · Alpine:v3.16 lxc · Alpine:v3.17 lxc · Alpine:v3.18 lxc · Alpine:v3.19 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Alpine:v3.14 lxc0 → 4.0.10-r2
  • Alpine:v3.15 lxc0 → 4.0.12-r2
  • Alpine:v3.16 lxc0 → 4.0.12-r2
  • Alpine:v3.17 lxc0 → 5.0.1-r2
  • Alpine:v3.18 lxc0 → 5.0.1-r2
  • Alpine:v3.19 lxc0 → 5.0.1-r2
  • Alpine:v3.20 lxc0 → 5.0.1-r2
  • Alpine:v3.21 lxc0 → 5.0.1-r2
  • Alpine:v3.22 lxc0 → 5.0.1-r2
  • Alpine:v3.23 lxc0 → 5.0.1-r2
  • Alpine:v3.24 lxc0 → 5.0.1-r2

How to fix CVE-2022-47952

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2022-47952. EPSS is 0.72%. Act only if a listed version of lxc-user-nic in lxc through is installed.

Which versions are affected?

Compare what you have installed with 0 → 4.0.10-r2, 0 → 4.0.12-r2, 0 → 5.0.1-r2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.72%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jan 1, 2023 · OpenSSF OSV / OSV Scanner

    Detected

    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 wa

  2. Oct 15, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    lxc fixed in 4.0.10-r2; lxc fixed in 4.0.12-r2; lxc fixed in 4.0.12-r2; lxc fixed in 5.0.1-r2

  3. Oct 15, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    lxc fixed in 4.0.10-r2

  4. Oct 15, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    lxc fixed in 4.0.12-r2

  5. Oct 15, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    lxc fixed in 5.0.1-r2

  6. Oct 15, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    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 wa

Sources

  • CVE.orgVulnerability recordCVE-2022-47952

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2022-47952

    30-day exploitation probability 0.7%

    first.org
  • OpenSSF OSV / OSV ScannerPackage advisoryALPINE-CVE-2022-47952
    osv.dev
  • Trivy Vulnerability DBPackage advisoryALPINE-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

    osv.dev

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.