Skip to content
OpenAdvisories
High SUSE-SU-2018:2688-1 4 CVEs

Security update for libzypp, zypper

Published Sep 11, 2018 · Updated Feb 4, 2026

Summary

This update for libzypp, zypper fixes the following issues:

libzypp security fixes:

- 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)
- Be sure bad packages do not stay in the cache (bsc#1045735, CVE-2017-9269)
- Fix repo gpg check workflows, mainly for unsigned repos and packages
(bsc#1045735, bsc#1038984, CVE-2017-7435, CVE-2017-7436, CVE-2017-9269)

libzypp other changes/bugs fixed:

- Update to version 14.45.17
- RepoInfo: add enum GpgCheck for convenient gpgcheck mode handling (bsc#1045735)
- repo refresh: Re-probe if the repository type changes (bsc#1048315)
- Use common workflow for downloading packages and srcpackages. This includes a
common way of handling and reporting gpg signature and checks. (bsc#1037210)
- PackageProvider: as well support downloading SrcPackage (for bsc#1037210)
- Adapt to work with GnuPG 2.1.23 (bsc#1054088)
- repo refresh: Re-probe if the repository type changes (bsc#1048315)
- Handle http error 502 Bad Gateway in curl backend (bsc#1070851)
- RepoManager: Explicitly request repo2solv to generate application pseudo
packages.
- Prefer calling 'repo2solv' rather than 'repo2solv.sh'
- 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)
- lsof: use '-K i' if lsof supports it (bsc#1099847, bsc#1036304)

zypper security fixes:

- 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)
- Adapt download callback to report and handle unsigned packages (bsc#1038984,
CVE-2017-7436)

zypper other changes/bugs fixed:

- Update to version 1.11.70
- Bugfix: Prevent ESC sequence strings from going out of scope (bsc#1092413)
- XML <install-summary> attribute `packages-to-change` added (bsc#1102429)
- man: Strengthen that `--config FILE' affects zypper.conf, not zypp.conf (bsc#1100028)
- ansi.h: Prevent ESC sequence strings from going out of scope (bsc#1092413)
- do not recommend cron (bsc#1079334)

Fixed packages 2

ReleasePackageFixed in
SUSE · SLES 12 Linux Enterprise Server 12-LTSS libzypp 14.45.17-2.82.1
SUSE · SLES 12 Linux Enterprise Server 12-LTSS zypper 1.11.70-2.69.2

Vulnerabilities 4

  • High 8.1

    libzypp accepts unsigned 3rd party repo without warning

    In libzypp before 20170803 it was possible to add unsigned YUM repositories without warning to the user that could lead to man in the middle or malicious servers to inject malicious RPM packages into a users system.

  • High 8.1

    libzypp accepts unsigned packages even when configured to check signatures

    In libzypp before 20170803 it was possible to retrieve unsigned packages without a warning to the user which could lead to man in the middle or malicious servers to inject malicious RPM packages into a users system.

  • 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/1037210
  • report
    https://bugzilla.suse.com/1038984
  • report
    https://bugzilla.suse.com/1045735
  • report
    https://bugzilla.suse.com/1048315
  • report
    https://bugzilla.suse.com/1054088
  • 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-7435
  • web
    https://www.suse.com/security/cve/CVE-2017-7436
  • web
    https://www.suse.com/security/cve/CVE-2017-9269
  • web
    https://www.suse.com/security/cve/CVE-2018-7685