The remote openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2024:0244-1 advisory.

    - Make sure, digest values handled by the Go library       github.com/opencontainers/go-digest and used throughout the       Go-implemented containers ecosystem are always validated. This       prevents attackers from triggering unexpected authenticated       registry accesses. (CVE-2024-3727, boo#1224114).


    - Updated apptainer to version 1.3.0
      * FUSE mounts are now supported in setuid mode, enabling full         functionality even when kernel filesystem mounts are insecure due to         unprivileged users having write access to raw filesystems in         containers. When allow `setuid-mount extfs = no` (the default) in         apptainer.conf, then the fuse2fs image driver will be used to mount         ext3 images in setuid mode instead of the kernel driver (ext3 images         are primarily used for the `--overlay` feature), restoring         functionality that was removed by default in Apptainer 1.1.8 because         of the security risk.
        The allow `setuid-mount squashfs` configuration option in         `apptainer.conf` now has a new default called `iflimited` which allows         kernel squashfs mounts only if there is at least one `limit container`         option set or if Execution Control Lists are activated in ecl.toml.
        If kernel squashfs mounts are are not allowed, then the squashfuse         image driver will be used instead.
        `iflimited` is the default because if one of those limits are used         the system administrator ensures that unprivileged users do not have         write access to the containers, but on the other hand using FUSE         would enable a user to theoretically bypass the limits via `ptrace()`         because the FUSE process runs as that user.
        The `fuse-overlayfs` image driver will also now be tried in setuid         mode if the kernel overlayfs driver does not work (for example if         one of the layers is a FUSE filesystem).  In addition, if `allow         setuid-mount encrypted = no` then the unprivileged gocryptfs format         will be used for encrypting SIF files instead of the kernel         device-mapper. If a SIF file was encrypted using the gocryptfs         format, it can now be mounted in setuid mode in addition to         non-setuid mode.
      * Change the default in user namespace mode to use either kernel         overlayfs or fuse-overlayfs instead of the underlay feature for the         purpose of adding bind mount points. That was already the default in         setuid mode; this change makes it consistent. The underlay feature         can still be used with the `--underlay` option, but it is deprecated         because the implementation is complicated and measurements have         shown that the performance of underlay is similar to overlayfs and         fuse-overlayfs.
        For now the underlay feature can be made the default again with a         new `preferred` value on the `enable underlay` configuration option.
        Also the `--underlay` option can be used in setuid mode or as the         root user, although it was ignored previously.
      * Prefer again to use kernel overlayfs over fuse-overlayfs when a         lower layer is FUSE and there's no writable upper layer, undoing the         change from 1.2.0. Another workaround was found for the problem that         change addressed. This applies in both setuid mode and in user         namespace mode.
      * `--cwd` is now the preferred form of the flag for setting the         container's working directory, though `--pwd` is still supported for         compatibility.
      * The way `--home` is handled when running as root (e.g. sudo apptainer)         or with `--fakeroot` has changed. Previously, we were only modifying         the `HOME` environment variable in these cases, while leaving the         container's `/etc/passwd` file unchanged (with its homedir field         pointing to `/root`, regardless of the value passed to `--home`). With         this change, both value of HOME and the contents of `/etc/passwd` in         the container will reflect the value passed to `--home` if the         container is readonly. If the container is writable, the         `/etc/passwd` file is left alone because it can interfere with         commands that want to modify it.
      * The `--vm` and related flags to start apptainer inside a VM have been         removed. This functionality was related to the retired Singularity Desktop         / SyOS projects.
      * The keyserver-related commands that were under `remote` have been moved to         their own, dedicated `keyserver` command. Run `apptainer help keyserver`         for more information.
      * The commands related to OCI/Docker registries that were under `remote` have         been moved to their own, dedicated `registry` command. Run         `apptainer help registry` for more information.
      * The the `remote list` subcommand now outputs only remote endpoints (with         keyservers and OCI/Docker registries having been moved to separate         commands), and the output has been streamlined.
      * Adding a new remote endpoint using the `apptainer remote add` command will         now set the new endpoint as default. This behavior can be suppressed by         supplying the `--no-default` (or `-n`) flag to `remote add`.
      * Skip parsing build definition file template variables after comments         beginning with a hash symbol.
      * The global `/tmp` directory is no longer used for gocryptfs mountpoints.
    - New Features & Functionality
      * The `remote status` command will now print the username, realname, and         email of the logged-in user, if available.
      * Add monitoring feature support, which requires the usage of an         additional tool named `apptheus`, this tool will put apptainer starter         into a newly created cgroup and collect system metrics.
      * A new `--no-pid` flag for `apptainer run/shell/exec` disables the PID         namespace inferred by `--containall` and `--compat`.
      * Added `--config` option to `keyserver` commands.
      * Honor an optional remoteName argument to the `keyserver list` command.
      * Added the `APPTAINER_ENCRYPTION_PEM_DATA` env var to allow for         encrypting and running encrypted containers without a PEM file.
      * Adding `--sharens` mode for `apptainer exec/run/shell`, which enables to         run multiple apptainer instances created by the same parent using         the same image in the same user namespace.
    - Make 'gocryptfs' an optional dependency.
    - Make apptainer definition templates version dependent.

    - Fix 'apptainer build' using signed packages from the SUSE       Registry (boo#1221364).

    - Updated apptainer to version 1.2.5
      * Added `libnvidia-nvvm` to `nvliblist.conf`. Newer NVIDIA         Drivers (known with >= 525.85.05) require this lib to compile         OpenCL programs against NVIDIA GPUs, i.e. `libnvidia-opencl`         depends on `libnvidia-nvvm`.
      * Disable the usage of cgroup in instance creation when         `--fakeroot` is passed.
      * Disable the usage of cgroup in instance creation when `hidepid`         mount option on `/proc` is set.
      * Fixed a regression introduced in 1.2.0 where the user's         password file information was not copied in to the container         when there was a parent root-mapped user namespace (as is the         case for example in `cvmfsexec`).
      * Added the upcoming NVIDIA driver library `libnvidia-gpucomp.so`         to the list of libraries to add to NVIDIA GPU-enabled         containers. Fixed missing error handling during the creation         of an encrypted image that lead to the generation of corrupted         images.
      * Use `APPTAINER_TMPDIR` for temporary files during privileged         image encryption.
      * If rootless unified cgroups v2 is available when starting an         image but `XDG_RUNTIME_DIR` or `DBUS_SESSION_BUS_ADDRESS` is         not set, print an info message that stats will not be available         instead of exiting with a fatal error.
      * Allow templated build arguments to definition files to have         empty values.
    - Package .def templates separately for different SPs.

    - Do not build squashfuse, require it as a dependency.
    - Replace awkward 'Obsoletes: singularity-*' as well as the       'Provides: Singularity' by 'Conflicts:' and drop the provides -       the versioning scheme does not match and we do not automatically       migrate from one to the other.
    - Exclude platforms which do not provide all build dependencies.

    - updated to 1.2.3 with following changes:
      * The apptainer push/pull commands now show a progress bar for the oras         protocol like there was for docker and library protocols.
      * The --nv and --rocm flags can now be used simultaneously.
      * Fix the use of APPTAINER_CONFIGDIR with apptainer instance start and action         commands that refer to instance://.
      * Fix the issue that apptainer would not read credentials from the Docker         fallback path ~/.docker/config.json if missing in the apptainer         credentials.

    - updated to 1.2.2 with following changes:
      * Fix $APPTAINER_MESSAGELEVEL to correctly set the logging level.
      * Fix build failures when in setuid mode and unprivileged user namespaces are         unavailable and the --fakeroot option is not selected.

    - updated to 1.2.1 to fix CVE-2023-38496 although not relevant as package is       compiled with setuid

    - update to 1.2.0 with following changes:
      * binary is built reproducible which disables plugins
      * Create the current working directory in a container when it doesn't exist.
        This restores behavior as it was before singularity 3.6.0. As a result,         using --no-mount home won't have any effect when running apptainer from a         home directory and will require --no-mount home,cwd to avoid mounting that         directory.
      * Handle current working directory paths containing symlinks both on the host         and in a container but pointing to different destinations. If detected, the         current working directory is not mounted when the destination directory in         the container exists.
      * Destination mount points are now sorted by shortest path first to ensure         that a user bind doesn't override a previous bind path when set in         arbitrary order on the CLI. This is also applied to image binds.
      * When the kernel supports unprivileged overlay mounts in a user namespace,         the container will be constructed by default using an overlay instead of an         underlay layout for bind mounts. A new --underlay action option can be used         to prefer underlay instead of overlay.
      * sessiondir maxsize in apptainer.conf now defaults to 64 MiB for new         installations. This is an increase from 16 MiB in prior versions.
      * The apptainer cache is now architecture aware, so the same home directory         cache can be shared by machines with different architectures.
      * Overlay is blocked on the panfs filesystem, allowing sandbox directories to         be run from panfs without error.
      * Lookup and store user/group information in stage one prior to entering any         namespaces, to fix an issue with winbind not correctly looking up         user/group information when using user namespaces.
    - New features / functionalities
      * Support for unprivileged encryption of SIF files using gocryptfs.  This is         not compatible with privileged encryption, so containers encrypted by root         need to be rebuilt by an unprivileged user.
      * Templating support for definition files. Users can now define variables in         definition files via a matching pair of double curly brackets. Variables of         the form {{ variable }} will be replaced by a value defined either by a         variable=value entry in the %arguments section of the definition file or         through new build options --build-arg or --build-arg-file.
      * Add a new instance run command that will execute the runscript when an         instance is initiated instead of executing the startscript.
      * The sign and verify commands now support signing and verification with         non-PGP key material by specifying the path to a private key via the --key         flag.
      * The verify command now supports verification with X.509 certificates by         specifying the path to a certificate via the --certificate flag. By         default, the system root certificate pool is used as trust anchors unless         overridden via the --certificate-roots flag. A pool of intermediate         certificates that are not trust anchors, but can be used to form a         certificate chain, can also be specified via the
        --certificate-intermediates flag.
      * Support for online verification checks of X.509 certificates using OCSP         protocol via the new verify --ocsp-verify option.
      * The instance stats command displays the resource usage every second. The
        --no-stream option disables this interactive mode and shows the         point-in-time usage.
      * Instances are now started in a cgroup by default, when run as root or when         unified cgroups v2 with systemd as manager is configured. This allows         apptainer instance stats to be supported by default when possible.
      * The instance start command now accepts an optional --app <name> argument         which invokes a start script within the %appstart <name> section in the         definition file. The instance stop command still only requires the instance         name.
      * The instance name is now available inside an instance via the new         APPTAINER_INSTANCE environment variable.
      * The --no-mount flag now accepts the value bind-paths to disable mounting of         all bind path entries in apptainer.conf.
        Support for DOCKER_HOST parsing when using docker-daemon://         DOCKER_USERNAME and DOCKER_PASSWORD supported without APPTAINER_ prefix.
        Add new Linux capabilities CAP_PERFMON, CAP_BPF, and CAP_CHECKPOINT_RESTORE.
      * The remote get-login-password command allows users to retrieve a remote's         token. This enables piping the secret directly into docker login while         preventing it from showing up in a shell's history.
      * Define EUID in %environment alongside UID.
      * In --rocm mode, the whole of /dev/dri is now bound into the container when
        --contain is in use. This makes /dev/dri/render devices available, required         for later ROCm versions.

    - update to 1.1.9 with following changes:
      * Remove warning about unknown xino=on option from fuse-overlayfs, introduced         in 1.1.8.
      * Ignore extraneous warning from fuse-overlayfs about a readonly /proc.
      * Fix dropped 'n' characters on some platforms in definition file stored as         part of SIF metadata.
      * Remove duplicated group ids.
      * Fix not being able to handle multiple entries in LD_PRELOAD when binding         fakeroot into container during apptainer startup for --fakeroot with         fakeroot command.

    - Included a fix for CVE-2023-30549 which is a vulnerability in setuid-root       installations of Apptainer iwhich was not active in the recent openSUSE       packages. Still this is included for completenss. The fix adds allow       setuid-mount configuration options encrypted, squashfs, and extfs, and makes       the default for extfs be 'no'. That disables the use of extfs mounts       including for overlays or binds while in the setuid-root mode, while leaving       it enabled for unprivileged user namespace mode. The default for encrypted       and squashfs is 'yes'.
    - Other bug fixes:
      * Fix loop device 'no such device or address' spurious errors when using shared         loop devices.
      * Add xino=on mount option for writable kernel overlay mount points to fix         inode numbers consistency after kernel cache flush (not applicable to         fuse-overlayfs).


    - updated to 1.1.7 with following changes:
      * Allow gpu options such as --nv to be nested by always inheriting all         libraries bound in to a parent container's /.singularity.d/libs.
      * Map the user's home directory to the root home directory by default in the         non-subuid fakeroot mode like it was in the subuid fakeroot mode, for both         action commands and building containers from definition files.
      * Make the error message more helpful in another place where a remote is         found to have no library client.
      * Avoid incorrect error when requesting fakeroot network.
      * Pass computed LD_LIBRARY_PATH to wrapped unsquashfs. Fixes issues where         unsquashfs on host uses libraries in non-default paths.

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

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

The remote host is affected by the vulnerability described in GLSA-202311-13 (Apptainer: Privilege Escalation)

  - Apptainer is an open source container platform for Linux. There is an ext4 use-after-free flaw that is     exploitable through versions of Apptainer < 1.1.0 and installations that include apptainer-suid < 1.1.8 on     older operating systems where that CVE has not been patched. That includes Red Hat Enterprise Linux 7,     Debian 10 buster (unless the linux-5.10 package is installed), Ubuntu 18.04 bionic and Ubuntu 20.04 focal.
    Use-after-free flaws in the kernel can be used to attack the kernel for denial of service and potentially     for privilege escalation. Apptainer 1.1.8 includes a patch that by default disables mounting of extfs     filesystem types in setuid-root mode, while continuing to allow mounting of extfs filesystems in non-     setuid rootless mode using fuse2fs. Some workarounds are possible. Either do not install apptainer-suid     (for versions 1.1.0 through 1.1.7) or set `allow setuid = no` in apptainer.conf. This requires having     unprivileged user namespaces enabled and except for apptainer 1.1.x versions will disallow mounting of sif     files, extfs files, and squashfs files in addition to other, less significant impacts. (Encrypted sif     files are also not supported unprivileged in apptainer 1.1.x.). Alternatively, use the `limit containers`     options in apptainer.conf/singularity.conf to limit sif files to trusted users, groups, and/or paths, and     set `allow container extfs = no` to disallow mounting of extfs overlay files. The latter option by itself     does not disallow mounting of extfs overlay partitions inside SIF files, so that's why the former options     are also needed. (CVE-2023-30549)

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

远程主机受到 GLSA-202311-13 中所述漏洞的影响（Apptainer：权限升级）

  - Apptainer 是一个适用于 Linux 的开源容器平台。Apptainer 版本低于 1.1.0 以及安装了 apptainer-suid 版本低于 1.1.8 的旧操作系统中存在 ext4 释放后使用漏洞。这个漏洞在尚未修补该 CVE 的旧操作系统上可以被利用。其中包括 Red Hat Enterprise Linux 7、Debian 10 buster（安装了 linux-5.10 软件包的操作系统除外）、Ubuntu 18.04 bionic 和 Ubuntu 20.04 focal。
    内核中存在释放后使用缺陷，攻击者可借此攻击内核以造成拒绝服务并可能导致特权提升。Apptainer 1.1.8 包含一个补丁，默认情况下禁用 setuid-root 模式下挂载 extfs 文件系统类型，同时继续允许使用 fuse2fs 在非 setuid 无根模式下挂载 extfs 文件系统。存在可用的解决方法。用户可选择不安装 apptainer-suid（对于版本 1.1.0 到 1.1.7）；或在 apptainer.conf 中设置“allow setuid = no”。要满足条件，需要启用非特权用户命名空间，并且除了 apptainer 1.1.x 版本外，还禁止挂载 sif 文件、extfs 文件和 squashfs 文件，此外还涉及其他一些较不重要的影响。（apptainer 1.1.x 中的非特权状态也不支持加密的 sif 文件。）。或者，使用 apptainer.conf/singularity.conf 中的“limit containers”选项将 sif 文件限制为受信任的用户、组和/或路径，并设置“allow container extfs = no”以禁止挂载 extfs 覆盖文件。后一个选项本身并不禁止在 SIF 文件内挂载 extfs 覆盖分区，这就是为什么还需要前一个选项。(CVE-2023-30549)

请注意，Nessus 尚未测试此问题，而是只依据应用程序自我报告的版本号进行判断。

遠端主機受到 GLSA-202311-13 中所述的弱點影響 (Apptainer：權限提升)

  - Apptainer 是適用於 Linux 的開放原始碼容器平台。在 Apptainer 1.1.0 之前版本以及尚未修補 CVE 的較舊作業系統上包含 apptainer-suid 1.1.8 之前版本的安裝中，ext4 中存在可利用的釋放後使用瑕疵。這包括 Red Hat Enterprise Linux 7、Debian 10 buster (除非已安裝 linux-5.10 套件)、Ubuntu 18.04 bionic 和 Ubuntu 20.04 focal。
    核心中的釋放後使用瑕疵可遭攻擊者用來攻擊核心，造成拒絕服務，並可能造成權限提升。Apptainer 1.1.8 中有一個修補程式預設為停用在 setuid-root 模式下掛載 extfs 檔案系統類型，同時繼續允許使用 fuse2fs 在非 setuid 無 root 模式下掛載 extfs 檔案系統。有一些可能的因應措施。不安裝 apptainer-suid (適用於 1.1.0 至 1.1.7 版)，或在 apptainer.conf 中設定 `allow setuid = no`。這需要啟用無權限的使用者命名空間，並且除了 apptainer 1.1.x 版本，也不允許掛載 sif 檔案、extfs 檔案和 squashfs 檔案，而且會造成其他較不重要的影響。(apptainer 1.1.x 中的無權限也不支援加密 sif 檔案。)。或者，使用 apptainer.conf/singularity.conf 中的「limit containers」選項，將 sif 檔案限制為受信任的使用者、群組和/或路徑，並將「allow container extfs = no」設定為不允許掛載 extfs 重疊檔案。後一個選項本身並不會禁止在 SIF 檔案內掛載 extfs 重疊磁碟分割，因此也需要前一個選項。(CVE-2023-30549)

請注意，Nessus 並未測試此問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

ID	名稱	產品	系列	已發布	已更新	嚴重性
205746	openSUSE 15 Security Update : apptainer (openSUSE-SU-2024:0244-1)	Nessus	SuSE Local Security Checks	2024/8/17	2024/8/17	high
186267	GLSA-202311-13 : Apptainer: Privilege Escalation	Nessus	Gentoo Local Security Checks	2023/11/25	2023/12/21	high
205746	openSUSE 15 のセキュリティ更新 : apptainer (openSUSE-SU-2024:0244-1)	Nessus	SuSE Local Security Checks	2024/8/17	2024/8/17	high
186267	GLSA-202311-13：Apptainer：权限提升	Nessus	Gentoo Local Security Checks	2023/11/25	2023/12/21	high
186267	GLSA-202311-13：Apptainer：權限提升	Nessus	Gentoo Local Security Checks	2023/11/25	2023/12/21	high

偵測

搜尋 Plugin

high

high

high

high

high