Описание
Security update for apptainer
This update for apptainer fixes the following issues:
Changes in apptainer:
-
Fix CVE-2026-39827, CVE-2026-39834, CVE-2026-39828, CVE-2026-39829, CVE-2026-39831, CVE-2026-42508, CVE-2026-39833, CVE-2026-39830, CVE-2026-39832, CVE-2026-46597, CVE-2026-46598, CVE-2026-46595, CVE-2026-39835 (bsc#1266202) Update golang.org/x/crypto to v0.52.0
-
Fix CVE-2026-33814 GO-2026-4918 (bsc#1265844) Update golang.org/x/net to version v0.53.0
-
Integrate vulnchecker into %check stage (optional).
-
Sync with Factory version which also fixes CVE-2024-45310 tracked in bsc#1257432
-
Readded SLE-15SP6.def as it was removed from Factory
Список пакетов
openSUSE Leap 16.0
Ссылки
- SUSE Security Ratings
- SUSE Bug 1257432
- SUSE Bug 1265844
- SUSE Bug 1266202
- SUSE CVE CVE-2024-45310 page
- SUSE CVE CVE-2026-33814 page
- SUSE CVE CVE-2026-39827 page
- SUSE CVE CVE-2026-39828 page
- SUSE CVE CVE-2026-39829 page
- SUSE CVE CVE-2026-39830 page
- SUSE CVE CVE-2026-39831 page
- SUSE CVE CVE-2026-39832 page
- SUSE CVE CVE-2026-39833 page
- SUSE CVE CVE-2026-39834 page
- SUSE CVE CVE-2026-39835 page
- SUSE CVE CVE-2026-42508 page
- SUSE CVE CVE-2026-46595 page
- SUSE CVE CVE-2026-46597 page
- SUSE CVE CVE-2026-46598 page
Описание
runc is a CLI tool for spawning and running containers according to the OCI specification. runc 1.1.13 and earlier, as well as 1.2.0-rc2 and earlier, can be tricked into creating empty files or directories in arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a race with `os.MkdirAll`. While this could be used to create empty files, existing files would not be truncated. An attacker must have the ability to start containers using some kind of custom volume configuration. Containers using user namespaces are still affected, but the scope of places an attacker can create inodes can be significantly reduced. Sufficiently strict LSM policies (SELinux/Apparmor) can also in principle block this attack -- we suspect the industry standard SELinux policy may restrict this attack's scope but the exact scope of protection hasn't been analysed. This is exploitable using runc directly as well as through Docker and Kubernetes. The issue is fixed in runc v1.1.14 and v1.2.0-rc3. Some workarounds are available. Using user namespaces restricts this attack fairly significantly such that the attacker can only create inodes in directories that the remapped root user/group has write access to. Unless the root user is remapped to an actual user on the host (such as with rootless containers that don't use `/etc/sub[ug]id`), this in practice means that an attacker would only be able to create inodes in world-writable directories. A strict enough SELinux or AppArmor policy could in principle also restrict the scope if a specific label is applied to the runc runtime, though neither the extent to which the standard existing policies block this attack nor what exact policies are needed to sufficiently restrict this attack have been thoroughly tested.
Затронутые продукты
Ссылки
- CVE-2024-45310
- SUSE Bug 1230092
- SUSE Bug 1257413
Описание
When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.
Затронутые продукты
Ссылки
- CVE-2026-33814
- SUSE Bug 1264506
Описание
An authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory growth, eventually crashing the server process and affecting all connected users. Rejected channels are now properly removed from the connection's internal state and released for garbage collection.
Затронутые продукты
Ссылки
- CVE-2026-39827
- SUSE Bug 1266049
Описание
When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil Permissions with PartialSuccessError now results in a connection error.
Затронутые продукты
Ссылки
- CVE-2026-39828
- SUSE Bug 1266049
Описание
The RSA and DSA public key parsers did not enforce size limits on key parameters. A crafted public key with an excessively large modulus or DSA parameter could cause several minutes of CPU consumption during signature verification. This could be triggered by unauthenticated clients during public key authentication. RSA moduli are now limited to 8192 bits, and DSA parameters are validated per FIPS 186-2.
Затронутые продукты
Ссылки
- CVE-2026-39829
- SUSE Bug 1266049
Описание
A malicious SSH peer could send unsolicited global request responses to fill an internal buffer, blocking the connection's read loop. The blocked goroutine could not be released by calling Close(), resulting in a resource leak per connection. Unsolicited global responses are now discarded.
Затронутые продукты
Ссылки
- CVE-2026-39830
- SUSE Bug 1266049
Описание
The Verify() method for FIDO/U2F security key types (sk-ecdsa-sha2-nistp256@openssh.com, sk-ssh-ed25519@openssh.com) did not check the User Presence flag. Signatures generated without physical touch were accepted, allowing unattended use of a hardware security key. To restore the previous behavior, return a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback.
Затронутые продукты
Ссылки
- CVE-2026-39831
- SUSE Bug 1266049
Описание
When adding a key to a remote agent constraint extensions such as restrict-destination-v00@openssh.com were not serialized in the request. Destination restrictions were silently stripped when forwarding keys, allowing unrestricted use of the key on the remote host. The client now serializes all constraint extensions. Additionally, the in-memory keyring returned by NewKeyring() now rejects keys with unsupported constraint extensions instead of silently ignoring them.
Затронутые продукты
Ссылки
- CVE-2026-39832
- SUSE Bug 1266049
Описание
The in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. The key would sign without any confirmation prompt, with no indication to the caller that the constraint was not in effect. NewKeyring() now returns an error when unsupported constraints are requested.
Затронутые продукты
Ссылки
- CVE-2026-39833
- SUSE Bug 1266049
Описание
When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.
Затронутые продукты
Ссылки
- CVE-2026-39834
- SUSE Bug 1266049
Описание
SSH servers which use CertChecker as a public key callback without setting IsUserAuthority or IsHostAuthority could be caused to panic by a client presenting a certificate. CertChecker now returns an error instead of panicking when these callbacks are nil.
Затронутые продукты
Ссылки
- CVE-2026-39835
- SUSE Bug 1266049
Описание
Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.
Затронутые продукты
Ссылки
- CVE-2026-42508
- SUSE Bug 1266049
Описание
Previously, CVE-2024-45337 fixed an authorization bypass for misused ssh server configurations; if any other type of callback is passed other than public key, then the source-address validation would be skipped.
Затронутые продукты
Ссылки
- CVE-2026-46595
- SUSE Bug 1266049
Описание
An incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs.
Затронутые продукты
Ссылки
- CVE-2026-46597
- SUSE Bug 1266049
Описание
For certain crafted inputs, a 'ed25519.PrivateKey' was created by casting malformed wire bytes, leading to a panic when used.
Затронутые продукты
Ссылки
- CVE-2026-46598
- SUSE Bug 1266049