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.

The remote openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the openSUSE- SU-2024:0342-1 advisory.

    lxc was updated to 6.0.2:

      The LXC team is pleased to announce the release of LXC 6.0.2!       This is the second bugfix release for LXC 6.0 which is supported       until June 2029.

      As usual this bugfix releases focus on stability and hardening.

      * Some of the highlights for this release are:

        - Reduced log level on some common messages
        - Fix compilation error on aarch64

      * Detailed changelog

        - Remove unused function
        - idmap: Lower logging level of newXidmap tools to INFO
        - Exit 0 when there's no error
        - doc: Fix definitions of get_config_path and set_config_path
        - README: Update security contact
        - fix possible clang compile error in AARCH

    Update to 6.0.1:

      The LXC team is pleased to announce the release of LXC 6.0.1!       This is the first bugfix release for LXC 6.0 which is supported       until June 2029.

      As usual this bugfix releases focus on stability and hardening.

      * Highlights

        - Fixed some build tooling issues
        - Fixed startup failures on system without IPv6 support
        - Updated AppArmor rules to avoid potential warnings

    Update to 6.0.0:

      The LXC team is pleased to announce the release of LXC 6.0 LTS!       This is the result of two years of work since the LXC 5.0 release       and is the sixth LTS release for the LXC project. This release       will be supported until June 2029.

      * New multi-call binary?

        A new tools-multicall=true configuration option can be used to         produce a single lxc binary which can then have all other         lxc-XYZ commands be symlinked to.
        This allows for a massive disk space reduction, particularly         useful for embedded platforms.

      * Add a set_timeout function to the library

        A new set_timeout function is available on the main         lxc_container struct and allow for setting a global timeout for         interactions with the LXC monitor.
        Prior to this, there was no timeout, leading to potential         deadlocks as there's also no way to cancel an monitor request.
        As a result of adding this new symbol to the library, we have         bumped the liblxc symbol version to 1.8.0.

      * LXC bridge now has IPV6 enabled

        The default lxcbr0 bridge now comes with IPv6 enabled by         default, using an IPv6 ULA subnet.
        Support for uid/gid selection in lxc-usernsexec         The lxc-usernsexec tool now has both -u and -g options to         control what resulting UID and GID (respectively) the user         wishes to use (defaulting to 0/0).

      * Improvements to lxc-checkconfig

        lxc-checkconfig now only shows the version if lxc-start is         present (rather than failing).
        Additionally, it's seen a number of other cosmetic improvements         as well as now listing the maximum number of allowed namespaces         for every namespace type.

      * Support for squashfs OCI images

        The built-in oci container template can now handle squashfs         compressed OCI images through the use of atomfs.

      * Switched from systemd's dbus to dbus-1

        LXC now uses libdbus-1 for DBus interactions with systemd         rather than using libsystemd.
        The reason for this change is that libdbus-1 is readily         available for static builds.

      * Removed Upstart support

        Support for the Upstart init system has finally been removed         from LXC.
        This shouldn't really affect anyone at this stage and allowed         for cleaning up some logic and config files from our         repository.

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Debian 10 host has packages installed that are affected by a vulnerability as referenced in the dla-3533 advisory.

  - 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)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

According to the versions of the lxc packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - 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)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
209977	openSUSE 15 Security Update : lxc (openSUSE-SU-2024:0342-1)	Nessus	SuSE Local Security Checks	low
179935	Debian DLA-3533-1 : lxc - LTS security update	Nessus	Debian Local Security Checks	low
177073	EulerOS 2.0 SP5 : lxc (EulerOS-SA-2023-2159)	Nessus	Huawei Local Security Checks	low
175267	EulerOS 2.0 SP11 : lxc (EulerOS-SA-2023-1763)	Nessus	Huawei Local Security Checks	low
175266	EulerOS 2.0 SP11 : lxc (EulerOS-SA-2023-1785)	Nessus	Huawei Local Security Checks	low
174187	EulerOS 2.0 SP8 : lxc (EulerOS-SA-2023-1600)	Nessus	Huawei Local Security Checks	low
172715	EulerOS 2.0 SP10 : lxc (EulerOS-SA-2023-1532)	Nessus	Huawei Local Security Checks	low
172708	EulerOS 2.0 SP10 : lxc (EulerOS-SA-2023-1557)	Nessus	Huawei Local Security Checks	low
172340	EulerOS 2.0 SP9 : lxc (EulerOS-SA-2023-1451)	Nessus	Huawei Local Security Checks	low
172330	EulerOS 2.0 SP9 : lxc (EulerOS-SA-2023-1476)	Nessus	Huawei Local Security Checks	low

Detections

Analytics

CVE-2022-47952

low

Tenable Plugins

low

low

low

low

low

low

low

low

low

low