Security update for rmt-server

SUSE Security Update: Security update for rmt-server
Announcement ID: SUSE-SU-2020:3036-1
Rating: important
References: #1165548 #1168554 #1172177 #1172182 #1172184 #1172186 #1173351
Cross-References:CVE-2019-16770 CVE-2019-5418 CVE-2019-5419 CVE-2019-5420 CVE-2020-11076 CVE-2020-11077 CVE-2020-15169 CVE-2020-5247 CVE-2020-5249 CVE-2020-5267 CVE-2020-8164 CVE-2020-8165 CVE-2020-8166 CVE-2020-8167 CVE-2020-8184 CVE-2020-8185
Affected Products:
  • SUSE Linux Enterprise Module for Server Applications 15-SP2
  • SUSE Linux Enterprise Module for Public Cloud 15-SP2

An update that fixes 16 vulnerabilities is now available.

Description:

This update for rmt-server fixes the following issues:
Update to version 2.6.5:

  • Solved potential bug of SCC repository URLs changing over time. RMT now self heals by removing the previous invalid repository and creating the correct one.
  • Add web server settings to /etc/rmt.conf: Now it's possible to configure the minimum and maximum threads count as well the number of web server workers to be booted through /etc/rmt.conf.
  • Instead of using an MD5 of URLs for custom repository friendly_ids, RMT now builds an ID from the name.
  • Fix RMT file caching based on timestamps: Previously, RMT sent GET requests with the header 'If-Modified-Since' to a repository server and if the response had a 304 (Not Modified), it would copy a file from the local cache instead of downloading. However, if the local file timestamp accidentally changed to a date newer than the one on the repository server, RMT would have an outdated file, which caused some errors. Now, RMT makes HEAD requests to the repositories servers and inspect the 'Last-Modified' header to decide whether to download a file or copy it from cache, by comparing the equalness of timestamps.
  • Fixed an issue where relative paths supplied to `rmt-cli import repos` caused the command to fail.
  • Friendlier IDs for custom repositories: In an effort to simplify the handling of SCC and custom repositories, RMT now has friendly IDs. For SCC repositories, it's the same SCC ID as before. For custom repositories, it can either be user provided or RMT generated (MD5 of the provided URL). Benefits:
    * `rmt-cli mirror repositories` now works for custom repositories. * Custom repository IDs can be the same across RMT instances. * No more confusing "SCC ID" vs "ID" in `rmt-cli` output. Deprecation Warnings:
    * RMT now uses a different ID for custom repositories than before. RMT still supports that old ID, but it's recommended to start using the new ID to ensure future compatibility.
  • Updated rails and puma dependencies for security fixes.

Patch Instructions:

To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Alternatively you can run the command listed for your product:

  • SUSE Linux Enterprise Module for Server Applications 15-SP2:
    zypper in -t patch SUSE-SLE-Module-Server-Applications-15-SP2-2020-3036=1
  • SUSE Linux Enterprise Module for Public Cloud 15-SP2:
    zypper in -t patch SUSE-SLE-Module-Public-Cloud-15-SP2-2020-3036=1

Package List:

  • SUSE Linux Enterprise Module for Server Applications 15-SP2 (aarch64 ppc64le s390x x86_64):
    • rmt-server-2.6.5-3.3.1
    • rmt-server-config-2.6.5-3.3.1
    • rmt-server-debuginfo-2.6.5-3.3.1
    • rmt-server-debugsource-2.6.5-3.3.1
  • SUSE Linux Enterprise Module for Public Cloud 15-SP2 (aarch64 ppc64le s390x x86_64):
    • rmt-server-debuginfo-2.6.5-3.3.1
    • rmt-server-debugsource-2.6.5-3.3.1
    • rmt-server-pubcloud-2.6.5-3.3.1

References: