Skip to content
OpenAdvisories
High SUSE-SU-2018:2716-2 2 CVEs

Security update for libzypp, zypper

Published Oct 18, 2018 · Updated Feb 4, 2026

Summary

This update for libzypp, zypper provides the following fixes:

Update libzypp to version 16.17.20

Security issues fixed:

- PackageProvider: Validate delta rpms before caching (bsc#1091624,
bsc#1088705, CVE-2018-7685)
- PackageProvider: Validate downloaded rpm package signatures before
caching (bsc#1091624, bsc#1088705, CVE-2018-7685)

Other bugs fixed:

- lsof: use '-K i' if lsof supports it (bsc#1099847, bsc#1036304)
- Handle http error 502 Bad Gateway in curl backend (bsc#1070851)
- RepoManager: Explicitly request repo2solv to generate application
pseudo packages.
- libzypp-devel should not require cmake (bsc#1101349)
- HardLocksFile: Prevent against empty commit without Target having
been been loaded (bsc#1096803)
- Avoid zombie tar processes (bsc#1076192)

Update to zypper to version 1.13.45

Security issue fixed:
- Improve signature check callback messages
(bsc#1045735, CVE-2017-9269)
- add/modify repo: Add options to tune the GPG check settings
(bsc#1045735, CVE-2017-9269)

Other bugs fixed:

- XML <install-summary> attribute `packages-to-change` added (bsc#1102429)
- man: Strengthen that `--config FILE' affects zypper.conf,
not zypp.conf (bsc#1100028)
- Prevent nested calls to exit() if aborted by a signal (bsc#1092413)
- ansi.h: Prevent ESC sequence strings from going out of scope (bsc#1092413)
- Fix: zypper bash completion expands non-existing options (bsc#1049825)
- do not recommend cron (bsc#1079334)
- Improve signature check callback messages (bsc#1045735)
- add/modify repo: Add options to tune the GPG check settings (bsc#1045735)

Fixed packages 2

ReleasePackageFixed in
SUSE · SLES 12 SP2 Linux Enterprise Server 12 SP2-BCL libzypp 16.17.20-27.52.1
SUSE · SLES 12 SP2 Linux Enterprise Server 12 SP2-BCL zypper 1.13.45-18.33.1

Vulnerabilities 2

  • High 7.8

    libzypp does not reevaluate malicious rpms once downloaded

    The decoupled download and installation steps in libzypp before 17.5.0 could lead to a corrupted RPM being left in the cache, where a later call would not display the corrupted RPM warning and allow installation, a problem caused by malicious warnings only di…

  • High 7.7

    lack of keypinning in libzypp could lead to repository switching

    In libzypp before August 2018 GPG keys attached to YUM repositories were not correctly pinned, allowing malicious repository mirrors to silently downgrade to unsigned repositories with potential malicious content.

References

  • report
    https://bugzilla.suse.com/1036304
  • report
    https://bugzilla.suse.com/1045735
  • report
    https://bugzilla.suse.com/1049825
  • report
    https://bugzilla.suse.com/1070851
  • report
    https://bugzilla.suse.com/1076192
  • report
    https://bugzilla.suse.com/1079334
  • report
    https://bugzilla.suse.com/1088705
  • report
    https://bugzilla.suse.com/1091624
  • report
    https://bugzilla.suse.com/1092413
  • report
    https://bugzilla.suse.com/1096803
  • report
    https://bugzilla.suse.com/1099847
  • report
    https://bugzilla.suse.com/1100028
  • report
    https://bugzilla.suse.com/1101349
  • report
    https://bugzilla.suse.com/1102429
  • web
    https://www.suse.com/security/cve/CVE-2017-9269
  • web
    https://www.suse.com/security/cve/CVE-2018-7685