ZeroDay Findings
Sign inSign up

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 · corrected/updated Oct 15, 2026 · evidence confidence high

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.

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2022-47952 is a low public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: lxc (0 → 4.0.10-r2); lxc (0 → 4.0.12-r2); lxc (0 → 4.0.12-r2); lxc (0 → 5.0.1-r2). Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: CVSS 3.3, EPSS 0.7%. It is not currently listed in the CISA Known Exploited catalog. Sources contributing to this record: cve_org, epss, osv, trivy. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.

  • Patch and remediation

    No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

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

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

  • 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