🛡️ openSUSE-SU-2023:0018-1 — apptainer (CVE-2022-39237 +2 more)

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Security update for apptainer

This update for apptainer fixes the following issues:

Updated to 1.1.2 which fixed CVE-2022-39237

  • CVE-2022-39237: The sif dependency included in Apptainer before this

release does not verify that the hash algorithm(s) used are

cryptographically secure when verifying digital signatures. This release

updates to sif v2.8.1 which corrects this issue. See the linked advisory

for references and a workaround.

Updated to version 1.1.0

  • added squashfuse-0.1.105.tar.gz and 70.patch for the build of squashfuse_ll

which will be removed as soon as the multithread patch is incoperated

  • Change squash mounts to prefer to use squashfuse_ll instead of squashfuse,

if available, for improved performance. squashfuse_ll is not available

in factory.

  • Also, for even better parallel performance, include a patched

multithreaded version of squashfuse_ll in

  • Imply adding ${prefix}/libexec/apptainer/bin to the binary path in

apptainer.conf, which is used for searching for helper executables. It is

implied as the first directory of $PATH if present (which is at the

beginning of binary path by default) or just as the first directory if

$PATH is not included in binary path.

${prefix}/libexec/apptainer/bin.

  • Add --unsquash action flag to temporarily convert a SIF file to a sandbox

before running. In previous versions this was the default when running a

SIF file without setuid or with fakeroot, but now the default is to instead

mount with squashfuse.

  • Add --sparse flag to overlay create command to allow generation of a sparse

ext3 overlay image.

  • Support for a custom hashbang in the %test section of an Apptainer recipe

(akin to the runscript and start sections).

  • When using fakeroot in setuid mode, have the image drivers first enter the

the container's user namespace to avoid write errors with overlays.

  • Skip trying to use kernel overlayfs when using writable overlay and the

lower layer is FUSE, because of a kernel bug introduced in kernel 5.15.

  • Add additional hidden options to the action command for testing different

fakeroot modes with --fakeroot: --ignore-subuid, --ignore-fakeroot-command,

and --ignore-userns.

  • Updated to version 1.1.0-rc2 with following changes:
  • Fixed longstanding bug in the underlay logic when there are nested bind

points separated by more than one path level, for example /var and

/var/lib/yum, and the path didn't exist in the container image. The bug

only caused an error when there was a directory in the container image that

didn't exist on the host.

  • Improved wildcard matching in the %files directive of build definition

files by replacing usage of sh with the mvdan.cc library.

  • Replaced checks for compatible filesystem types when using fuse-overlayfs

with an INFO message when an incompatible filesystem type causes it to be

unwritable by a fakeroot user.

  • The --nvccli option now works without --fakeroot. In that case the option

can be used with --writable-tmpfs instead of --writable, and

--writable-tmpfs is implied if neither option is given. Note that also

/usr/bin has to be writable by the user, so without --fakeroot that

probably requires a sandbox image that was built with --fix-perms.

  • The --nvccli option implies --nv.
  • Configure squashfuse to always show files to be owned by the current user.

That's especially important for fakeroot to prevent most of the files from

looking like they are owned by user 65534.

  • The fakeroot command can now be used even if $PATH is empty in the

environment of the apptainer command.

  • Allow the newuidmap command to be missing if the current user is not listed

in /etc/subuid.

  • Require the uidmap package in Debian packaging.
  • Improved error handling of unsupported pass protected PEM files with

encrypted containers.

  • Ensure bootstrap_history directory is populated with previous definition

files, present in source containers used in a build.

  • Add additional options to the build command for testing different fakeroot

modes: --userns like the action flag and hidden options --ignore-subuid,

--ignore-fakeroot-command, and --ignore-userns.

  • Require root user early when building an encrypted container.
  • removed upstream incorated patch fix-32bit-compilation.patch
  • Updated to version 1.1.0-rc1 which enables apptainer to run without

suid and additional groups. Although this is a prerelease this is

a major advantage justifying its use.

  • Added a squashfuse image driver that enables mounting SIF files without

using setuid-root. Requires the squashfuse command and unprivileged user

namespaces.

  • Added a fuse2fs image driver that enables mounting EXT3 files and EXT3 SIF

overlay partitions without using setuid-root. Requires the fuse2fs command

and unprivileged user namespaces.

  • Added the ability t

Affected software

openSUSE-SU-2023:0018-1 is recorded against 1 package.

  • apptainer (fixed in 1.1.2-lp154.2.1)

Timeline and source

Published on 15 January 2023 and last revised on 4 February 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

lists.opensuse.org (Advisory)
www.suse.com (Web)
www.suse.com (Web)
www.suse.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2023-01-15
Updated 2026-08-20
Modified 2026-02-04
Fix URL N/A

Affected Packages

Software From version Fixed in
apptainer 1.1.2-lp154.2.1

Free Vulnerability Check

Is your site affected by openSUSE-SU-2023:0018-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against openSUSE-SU-2023:0018-1 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesSUSESUSE 2023