Findings

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 · updated Oct 15, 2026

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.

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 · OSV.dev

    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 · OSV.dev

    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 · OSV.dev

    Fix available

    lxc fixed in 4.0.10-r2

  4. Oct 15, 2026 · OSV.dev

    Fix available

    lxc fixed in 4.0.12-r2

  5. Oct 15, 2026 · OSV.dev

    Fix available

    lxc fixed in 5.0.1-r2

  6. Oct 15, 2026 · OSV.dev

    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

Affected

  • 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

Sources

References