Skip to content
Noroxi
CVE-2022-47952· NVD / CVE Program· CNA mitre

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 protec

Noroxi assessment

Priority: Monitor (action score 13/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.72% (FIRST EPSS); higher than 53.1% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: lxc (Alpine:v3.14) 4.0.10-r2; lxc (Alpine:v3.15) 4.0.12-r2; lxc (Alpine:v3.17) 5.0.1-r2.

Low priority for now. Upgrade to lxc (Alpine:v3.14) 4.0.10-r2; lxc (Alpine:v3.15) 4.0.12-r2; lxc (Alpine:v3.17) 5.0.1-r2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

LowCVSS 3.3 · v3.1—Proof of concept Fix available
Published
Jan 1, 2023
Updated
Jun 17, 2026
EPSS
0.7% · 53th percentile

Report tools

JSON

Action score

13

Monitor

Low priority for now.

CVSS
13 / 40 · 3.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-47952

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linuxcontainers records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxcontainerslxc

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linuxcontainers lxcup to 5.0.1 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.14lxcbefore 4.0.10-r24.0.10-r2
Alpine:v3.15lxcbefore 4.0.12-r24.0.12-r2
Alpine:v3.17lxcbefore 5.0.1-r25.0.1-r2
Debian:10lxcbefore 1:3.1.0+really3.0.3-8+deb10u11:3.1.0+really3.0.3-8+deb10u1
Debian:12lxcbefore 1:5.0.2-11:5.0.2-1
openSUSE:Tumbleweedlxcbefore 5.0.2-1.15.0.2-1.1
SUSE:Package Hub 15 SP5lxcbefore 6.0.2-bp156.2.3.16.0.2-bp156.2.3.1
SUSE:Package Hub 15 SP5lxcbefore 6.0.2-bp156.2.3.16.0.2-bp156.2.3.1

Same product

linuxcontainers: all records

Other highest-scoring records for the same primary product.

  • CVE-2016-8649lxc-attach in LXC before 1.0.9 and 2.x before 2.0.6 allows an attacker inside of an unprivileged container to use an inherited file descript
    37Monitor
  • CVE-2016-10124An issue was discovered in Linux Containers (LXC) before 2016-02-22.
    34Monitor
  • CVE-2017-18641In LXC 2.0, many template scripts download code over cleartext HTTP, and omit a digital-signature check, before running it to bootstrap cont
    32Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2015-1335Oct 1, 2015 · lxc-start in lxc before 1.0.8 and 1.1.x before 1.1.4 allows local container administrators to escape AppArmor confinement via a symlink atta
    28Monitor
  • ← EarlierCVE-2017-5985Mar 14, 2017 · lxc-user-nic in Linux Containers (LXC) allows local users with a lxc-usernet allocation to create network interfaces on the host and choose
    13Monitor
  • Later →CVE-2026-39402May 5, 2026 · lxc lxc-user-nic insufficient ownership validation allows cross-tenant OVS port deletion
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:lxc4.0.10-r2 · Alpine:v3.14Package registry (OSV)
debian:lxc1:5.0.2-1 · Debian:12Package registry (OSV)
opensuse:lxc6.0.2-bp156.2.3.1 · openSUSE:Leap 15.5Package registry (OSV)
suse:lxc6.0.2-bp156.2.3.1 · SUSE:Package Hub 15 SP5Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02022-12-31

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-1 d
  2. Published
  3. TodayOct 20, 2026+1389 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-203 · Observable Discrepancy

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records