SUSE-SU-2022:1128-1 Security update for libsolv, libzypp
Not scored
Published
Check this codebase for SUSE-SU-2022:1128-1 and fix it if it is affected.
What it is: SUSE-SU-2022:1128-1 is a memory corruption vulnerability in libsolv, published on 7 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2022:1128-1 in the wild and no public exploit code.
Affected product: libsolv. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/SUSE-SU-2022-1128-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2022-1128-1/index.md)
A memory corruption vulnerability in SUSE's package manager libraries allows attackers to cause a denial of service via crafted package metadata.
- 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:1128-1?
SUSE-SU-2022:1128-1 is a memory corruption vulnerability in libsolv, published on 7 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 fixes the following issues:
libsolv to 0.6.39:
- fix memory leaks in SWIG generated code
- fix misparsing of '&' in attributes with libxml2
- try to keep packages from a cycle close togther in the transaction order (bsc#1189622)
- fix split provides not working if the update includes a forbidden vendor change (bsc#1195485)
- fix segfault on conflict resolution when using bindings
- do not replace noarch problem rules with arch dependent ones in problem reporting
- fix and simplify pool_vendor2mask implementation
- bump version to 0.6.39
libzypp to 16.22.4:
- Hint on ptf resolver conflicts (bsc#1194848)
- 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.
- Set ZYPP_RPM_DEBUG=1 to capture verbose rpm command output.
Which versions are affected by SUSE-SU-2022:1128-1?
Linux distribution packages (2)
libsolv SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 0.6.39-2.27.32.2 |
libzypp SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 16.22.4-27.85.2 |
How do I fix SUSE-SU-2022:1128-1?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is SUSE-SU-2022:1128-1 being exploited?
There is no known exploitation of SUSE-SU-2022:1128-1 in the wild and no public exploit code.