OESA-2023-1077 (CVE-2022-47952)
Vulnerability from osv_openeuler – Published: 2023-02-10 11:05 – Updated: 2026-08-06 11:05 – Source websiteContainers are insulated areas inside a system, which have their own namespace for filesystem, network, PID, IPC, CPU and memory allocation and which can be created using the Control Group and Namespace features included in the Linux kernel.
Security Fix(es):
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.(CVE-2022-47952)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"lxc-devel-4.0.3-2022102408.oe2203sp1.aarch64.rpm",
"lxc-libs-4.0.3-2022102408.oe2203sp1.aarch64.rpm",
"lxc-debugsource-4.0.3-2022102408.oe2203sp1.aarch64.rpm",
"lxc-debuginfo-4.0.3-2022102408.oe2203sp1.aarch64.rpm",
"lxc-4.0.3-2022102408.oe2203sp1.aarch64.rpm"
],
"noarch": [
"lxc-help-4.0.3-2022102408.oe2203sp1.noarch.rpm"
],
"src": [
"lxc-4.0.3-2022102408.oe2203sp1.src.rpm"
],
"x86_64": [
"lxc-debuginfo-4.0.3-2022102408.oe2203sp1.x86_64.rpm",
"lxc-debugsource-4.0.3-2022102408.oe2203sp1.x86_64.rpm",
"lxc-libs-4.0.3-2022102408.oe2203sp1.x86_64.rpm",
"lxc-4.0.3-2022102408.oe2203sp1.x86_64.rpm",
"lxc-devel-4.0.3-2022102408.oe2203sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP1",
"name": "lxc",
"purl": "pkg:rpm/openEuler/lxc\u0026distro=openEuler-22.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.0.3-2022102408.oe2203sp1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Low"
},
"details": "Containers are insulated areas inside a system, which have their own namespace for filesystem, network, PID, IPC, CPU and memory allocation and which can be created using the Control Group and Namespace features included in the Linux kernel.\r\n\r\nSecurity Fix(es):\r\n\r\nlxc-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 \u0026quot;Failed to open\u0026quot; often indicates that a file does not exist, whereas \u0026quot;does not refer to a network namespace path\u0026quot; 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 \u0026quot;we will report back to the user that the open() failed but the user has no way of knowing why it failed\u0026quot;; however, in many realistic cases, there are no plausible reasons for failing except that the file does not exist.(CVE-2022-47952)",
"id": "OESA-2023-1077",
"modified": "2026-08-06T11:05:33Z",
"published": "2023-02-10T11:05:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1077"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-47952"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "lxc security update",
"upstream": [
"CVE-2022-47952"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.