SUSE-SU-2022:1130-1 Security update for libsolv, libzypp, zypper
Attackers can bypass package signature checks in SUSE package managers, potentially installing malicious software without detection.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is SUSE-SU-2022:1130-1?
SUSE-SU-2022:1130-1 is a vulnerability in libsolv, published on 8 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
This update for libsolv, libzypp, zypper fixes the following issues:
Security relevant fix:
- Harden package signature checks (bsc#1184501).
libsolv to 0.7.22:
reworked choice rule generation to cover more usecases
support SOLVABLE_PREREQ_IGNOREINST in the ordering code (bsc#1196514)
support parsing of Debian's Multi-Arch indicator
fix segfault on conflict resolution when using bindings
fix split provides not working if the update includes a forbidden vendor change
support strict repository priorities new solver flag: SOLVER_FLAG_STRICT_REPO_PRIORITY
support zstd compressed control files in debian packages
add an ifdef allowing to rename Solvable dependency members ('requires' is a keyword in C++20)
support setting/reading userdata in solv files new functions: repowriter_set_userdata, solv_read_userdata
support queying of the custom vendor check function new function: pool_get_custom_vendorcheck
support solv files with an idarray block
allow accessing the toolversion at runtime
libzypp to 17.30.0:
- ZConfig: Update solver settings if target changes (bsc#1196368)
- Fix possible hang in singletrans mode (bsc#1197134)
- Do 2 retries if mount is still busy.
- Fix package signature check (bsc#1184501) Pay attention that header and payload are secured by a valid signature and report more detailed which signature is missing.
- Retry umount if device is busy (bsc#1196061, closes #381) A previously released ISO image may need a bit more time to release it's loop device. So we wait a bit and retry.
- Fix serializing/deserializing type mismatch in zypp-rpm protocol (bsc#1196925)
- Fix handling of ISO media in releaseAll (bsc#1196061)
- Hint on common ptf resolver conflicts (bsc#1194848)
- Hint on ptf<>patch resolver conflicts (bsc#1194848)
zypper to 1.14.52:
- info: print the packages upstream URL if available (fixes #426)
- info: Fix SEGV with not installed PTFs (bsc#1196317)
- Don't prevent less restrictive umasks (bsc#1195999)
Which versions are affected by SUSE-SU-2022:1130-1?
Linux distribution packages (15)
libsolv SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 0.7.22-150000.3.51.1 |
libzypp SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 17.30.0-150000.3.95.1 |
zypper SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 1.14.52-150000.3.69.2 |
libsolv SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 0.7.22-150000.3.51.1 |
libzypp SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 17.30.0-150000.3.95.1 |
zypper SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 1.14.52-150000.3.69.2 |
libsolv SUSE:Linux Enterprise Installer Updates 15 | All versions | 0.7.22-150000.3.51.1 |
libzypp SUSE:Linux Enterprise Installer Updates 15 | All versions | 17.30.0-150000.3.95.1 |
zypper SUSE:Linux Enterprise Installer Updates 15 | All versions | 1.14.52-150000.3.69.2 |
libsolv SUSE:Linux Enterprise Server 15-LTSS | All versions | 0.7.22-150000.3.51.1 |
libzypp SUSE:Linux Enterprise Server 15-LTSS | All versions | 17.30.0-150000.3.95.1 |
zypper SUSE:Linux Enterprise Server 15-LTSS | All versions | 1.14.52-150000.3.69.2 |
libsolv SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 0.7.22-150000.3.51.1 |
libzypp SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 17.30.0-150000.3.95.1 |
zypper SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 1.14.52-150000.3.69.2 |
How do I fix SUSE-SU-2022:1130-1?
Apply the vendor's patch.
Is SUSE-SU-2022:1130-1 being exploited?
There is no known exploitation of SUSE-SU-2022:1130-1 in the wild and no public exploit code.