# CVE-2022-47952: Information disclosure in n/a

> Local attackers can infer file existence in protected directories via error message differences in the setuid lxc-user-nic binary.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** ALPINE-CVE-2022-47952, DEBIAN-CVE-2022-47952, DLA-3533-1, GHSA-qv29-rjwj-jjrm, OESA-2023-1075, OESA-2023-1076, OESA-2023-1077, UBUNTU-CVE-2022-47952, openSUSE-SU-2024:0342-1, openSUSE-SU-2024:12935-1

## What is CVE-2022-47952?

CVE-2022-47952 is a low-severity vulnerability in n/a, published on 1 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2022-47952?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lxc` | SUSE:Package Hub 15 SP5 | All versions | 6.0.2-bp156.2.3.1 |
| `lxc` | SUSE:Package Hub 15 SP6 | All versions | 6.0.2-bp156.2.3.1 |
| `lxc` | openSUSE:Leap 15.5 | All versions | 6.0.2-bp156.2.3.1 |
| `lxc` | openSUSE:Leap 15.6 | All versions | 6.0.2-bp156.2.3.1 |
| `lxc` | openSUSE:Tumbleweed | All versions | 5.0.2-1.1 |

Products: Linuxcontainers Lxc.

## How do I fix CVE-2022-47952?

Apply the vendor's patch.

## Is CVE-2022-47952 being exploited?

There is no known exploitation of CVE-2022-47952 in the wild and no public exploit code.

Public exploit code:

- LXC Information Disclosure vulnerability. (github_poc): https://github.com/MaherAzzouzi/CVE-2022-47952

## Other vulnerabilities in n/a

- [CVE-2016-8649](https://insights.sbomify.com/CVE-2016-8649/): Path traversal in LXC before 1.0.9 and 2.x before 2.0.6 (critical 9.1)
- [CVE-2016-10124](https://insights.sbomify.com/CVE-2016-10124/): Privilege escalation in n/a (high 8.6)
- [CVE-2017-18641](https://insights.sbomify.com/CVE-2017-18641/): Supply chain in n/a (high 8.1)
- [CVE-2013-6441](https://insights.sbomify.com/CVE-2013-6441/): Privilege escalation in n/a (high 7.2)
- [CVE-2015-1331](https://insights.sbomify.com/CVE-2015-1331/): Path traversal in n/a (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47952 and fix it if it is affected.

What it is: CVE-2022-47952 is a low-severity vulnerability in n/a, published on 1 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-47952 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-47952/ (Markdown: https://insights.sbomify.com/CVE-2022-47952/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-47952
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-47952
- OSV: https://osv.dev/vulnerability/CVE-2022-47952

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-47952/
Summaries are generated and may contain mistakes; the official description above is the record.