An update for lxc is now available for openEuler-22.03-LTS-SP1 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2023-1077 Final 1.0 1.0 2023-02-10 Initial 2023-02-10 2023-02-10 openEuler SA Tool V1.0 2023-02-10 lxc security update An update for lxc is now available for openEuler-22.03-LTS-SP1. 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. 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) An update for lxc is now available for openEuler-22.03-LTS-SP1. openEuler Security has rated this update as having a security impact of low. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. Low lxc https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1077 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2022-47952 https://nvd.nist.gov/vuln/detail/CVE-2022-47952 openEuler-22.03-LTS-SP1 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 lxc-help-4.0.3-2022102408.oe2203sp1.noarch.rpm lxc-4.0.3-2022102408.oe2203sp1.src.rpm 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 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. 2023-02-10 CVE-2022-47952 openEuler-22.03-LTS-SP1 Low 3.3 AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N lxc security update 2023-02-10 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1077