CVE-2020-8184

A reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it possible for an attacker to forge a secure or host-only cookie prefix.

Rack provides a minimal, modular, and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses in the simplest way possible, it unifies and distills the API for web servers, web frameworks, and software in between (the so-called middleware) into a single method call.

Security Fix(es):

Denial of Service Vulnerability in Rack Multipart Parsing(CVE-2022-30122)

Possible shell escape sequence injection vulnerability in Rack(CVE-2022-30123)

A reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it is possible for an attacker to forge a secure or host-only cookie prefix.(CVE-2020-8184)

A reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it is possible for an attacker to forge a secure or host-only cookie prefix.

A reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3 that makes it is possible for an attacker to forge a secure or host-only cookie prefix (CVE-2020-8184).

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.

This update was imported from the SUSE:SLE-15-SP2:Update update project.

This update for rmt-server fixes the following issues:

• 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.

• Version 2.6.4

• 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.

• Version 2.6.3

• Instead of using an MD5 of URLs for custom repository friendly_ids, RMT now builds an ID from the name.

• Version 2.6.2

• 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.

• Version 2.6.1

• Fixed an issue where relative paths supplied to rmt-cli import repos caused the command to fail.

• Version 2.6.0

• 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.

• Version 2.5.20

• Updated rails from 6.0.3.2 to 6.0.3.3:

  • actionview (CVE-2020-15169)

• Version 2.5.19

• RMT now has the ability to remove local systems with the command rmt-cli systems remove.

• Version 2.5.18

• Fixed exit code for rmt-cli mirror and its subcommands. Now it exits with 1 whenever an error occurs during mirroring

• Improved message logging for rtm-cli mirror. Instead of logging an error when it occurs, the command summarize all errors at the end of execution. Now log messages have colors to better identify failure/success.

• Version 2.5.17

• RMT no longer provides the installer updates repository to systems via its zypper service. This repository is used during the installation process, as it provides an up-to-date installation experience, but it has no use on an already installed system.

• Version 2.5.16

• Updated RMT's rails and puma dependencies.

  • puma (CVE-2020-11076, CVE-2020-11077, CVE-2020-5249, CVE-2020-5247 CVE-2019-16770)
  • actionpack (CVE-2020-8185, CVE-2020-8164, CVE-2020-8166)
  • actionview (CVE-2020-8167, CVE-2020-5267, CVE-2019-5418, CVE-2019-5419)
  • activesupport (CVE-2020-8165)
  • railties (CVE-2019-5420)

• Version 2.5.15

• RMT now checks if repositories are fully mirrored during the activation process. Previously, RMT only checked if the repositories were enabled to be mirrored, but not that they were actually mirrored. In this case, RMTs were not able to provide the repository data which systems assumed it had.

• Version 2.5.14

• Enable 'Installer-Updates' repositories by default

• Fixed deprecation warning when thor encountered an error. Also, instead of returning 0 for thor errors, rmt-cli will return 1 instead.

• Version 2.5.13

• Added rmt-cli repos clean command to remove locally mirrored files of repositories which are not marked to be mirrored.

• Previously, RMT didn't track…

These are all security issues fixed in the rmt-server-2.6.13-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby2.7-rubygem-rack-2.2.3-1.7 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.1-rubygem-rack-2.2.3.1-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.1-rubygem-rack-2.2-2.2.4-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.2-rubygem-rack-2.2-2.2.7-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.2-rubygem-rack-3.0.7-1.2 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.3-rubygem-rack-3.0.9.1-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.3-rubygem-rack-2.2-2.2.8.1-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.4-rubygem-rack-2.2-2.2.11-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.4-rubygem-rack-3.1.12-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby4.0-rubygem-rack-2.2-2.2.22-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby4.0-rubygem-rack-3.1.18-1.3 package on the GA media of openSUSE Tumbleweed.

This update for ansible1, ardana-ansible, ardana-cobbler, ardana-glance, ardana-input-model, ardana-logging, ardana-manila, ardana-monasca, ardana-mq, ardana-neutron, ardana-octavia, ardana-tempest, crowbar-core, crowbar-openstack, grafana, kibana, openstack-barbican, openstack-ceilometer, openstack-cinder, openstack-dashboard, openstack-designate, openstack-heat-templates, openstack-ironic, openstack-keystone, openstack-magnum, openstack-manila, openstack-monasca-agent, openstack-neutron, openstack-neutron-vsphere, openstack-nova, openstack-octavia, openstack-octavia-amphora-image, openstack-resource-agents, python-Django1, python-Pillow, python-ardana-packager, python-heatclient, python-neutron-tempest-plugin, python-octavia-tempest-plugin, python-os-brick, python-oslo.messaging, python-pyroute2, python-urllib3, python-waitress, release-notes-suse-openstack-cloud, rubygem-activeresource, rubygem-json-1_7, rubygem-puma fixes the following issues:

Security fixes included in this update:

ansible1:

• CVE-2019-3828: Fixed a path traversal in the fetch module (bsc#1126503).

grafana:

• CVE-2020-13379: Fixed an incorrect access control issue which could lead to information leaks or denial of service (bsc#1172409).
• CVE-2020-12052: Fixed an cross site scripting vulnerability related to the annotation popup (bsc#1170657).

kibana:

• CVE-2020-10743: Fixed a clickjacking vulnerability (bsc#1171909).

python-Django1 to 1.11.29:

• CVE-2020-13254: Fixed a data leakage via malformed memcached keys (bsc#1172167).
• CVE-2020-13596: Fixed a cross site scripting vulnerability related to the admin parameters of the ForeignKeyRawIdWidget (bsc#1172166).
• CVE-2020-7471: Fixed a SQL injection via StringAgg delimiter (bsc#1161919).
• CVE-2020-9402: Fixed a SQL injection via tolerance parameter in GIS functions and aggregates (bsc#1165022).
• CVE-2019-19844: Fixed a potential account hijack via password reset form (bsc#1159447).

python-Pillow:

• CVE-2020-10177: Fixed multiple out-of-bounds reads in libImaging/FliDecode.c (bsc#1173413).
• CVE-2020-11538: Fixed multiple out-of-bounds reads via a crafted JP2 files (bsc#1173420).
• CVE-2020-10994: Fixed multiple out-of-bounds reads via a crafted JP2 files (bsc#1173418).
• CVE-2020-10378: Fixed an out-of-bounds read when reading PCX files (bsc#1173416).
• CVE-2019-16865: Fixed a denial of service with specially crafted image files (bsc#1153191).
• CVE-2020-5311: Fixed an SGI buffer overflow (bsc#1160151).
• CVE-2020-5312: Fixed a buffer overflow in the PCX P mode (bsc#1160152).
• CVE-2020-5313: Fixed a buffer overflow related to FLI (bsc#1160153).
• CVE-2019-19911: Fixed a denial of service in FpxImagePlugin.py (bsc#1160192).

python-waitress to version 1.4.3:

• CVE-2019-16785: Fixed HTTP request smuggling through LF vs CRLF handling (bsc#1161088).
• CVE-2019-16786: Fixed HTTP request smuggling through invalid Transfer-Encoding (bsc#1161089).
• CVE-2019-16789: Fixed HTTP Request Smuggling through invalid whitespace characters (bsc#1160790).
• CVE-2019-16792: Fixed HTTP Request Smuggling through Content-Length header handling (bsc#1161670).

rubygem-activeresource:

• CVE-2020-8151: Fixed possible information disclosure through specially crafted requests (bsc#1171560).

Non security fixes:

Changes in ansible1.SUSE_SLE-12-SP4_Update_Products_Cloud9_Update:

• Add 0001-Disallow-use-of-remote-home-directories-containing-..patch (bsc#1126503, CVE-2019-3828)

Changes in ardana-ansible.SUSE_SLE-12-SP4_Update_Products_Cloud9_Update:

• Update to version 9.0+git.1591138508.e269bdb:

  • Use internal endpoint for upload image (SOC-11294)

• Update to version 9.0+git.1589740968.d339a28:

  • Reconfigure rabbitmq user permissions on update (SOC-11082)

• Update to version 9.0+git.1588953276.b8b5512:

  • Fix incorrect prefix used to collect supportconfig files (bsc#1171273)

Changes in ardana-cobbler.SUSE_SLE-12-SP4_Update_Products_Cloud9_Update:

• Update to version 9.0+git.1588181228.bae3b1f:
  • Ensure…

This update for rubygem-rack to version 1.6.13 fixes the following issues:

• CVE-2020-8184: Fixed an issue where percent-encoded cookies could have been used to overwrite existing prefixed cookie names (bsc#1173351).
• CVE-2020-8161: Fixed a directory traversal (bsc#1172037).
• CVE-2019-16782: Fixed an information leak / session hijack vulnerability (bsc#1159548).

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.

This update for rmt-server fixes the following issues:

• 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.

• Version 2.6.4

• 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.

• Version 2.6.3

• Instead of using an MD5 of URLs for custom repository friendly_ids, RMT now builds an ID from the name.

• Version 2.6.2

• 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.

• Version 2.6.1

• Fixed an issue where relative paths supplied to rmt-cli import repos caused the command to fail.

• Version 2.6.0

• 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.

• Version 2.5.20

• Updated rails from 6.0.3.2 to 6.0.3.3:

  • actionview (CVE-2020-15169)

• Version 2.5.19

• RMT now has the ability to remove local systems with the command rmt-cli systems remove.

• Version 2.5.18

• Fixed exit code for rmt-cli mirror and its subcommands. Now it exits with 1 whenever an error occurrs during mirroring

• Improved message logging for rtm-cli mirror. Instead of logging an error when it occurs, the command summarize all errors at the end of execution. Now log messages have colors to better identify failure/success.

• Version 2.5.17

• RMT no longer provides the installer updates repository to systems via its zypper service. This repository is used during the installation process, as it provides an up-to-date installation experience, but it has no use on an already installed system.

• Version 2.5.16

• Updated RMT's rails and puma dependencies.

  • puma (CVE-2020-11076, CVE-2020-11077, CVE-2020-5249, CVE-2020-5247 CVE-2019-16770)
  • actionpack (CVE-2020-8185, CVE-2020-8164, CVE-2020-8166)
  • actionview (CVE-2020-8167, CVE-2020-5267, CVE-2019-5418, CVE-2019-5419)
  • activesupport (CVE-2020-8165)
  • railties (CVE-2019-5420)

• Version 2.5.15

• RMT now checks if repositories are fully mirrored during the activation process. Previously, RMT only checked if the repositories were enabled to be mirrored, but not that they were actually mirrored. In this case, RMTs were not able to provide the repository data which systems assumed it had.

• Version 2.5.14

• Enable 'Installer-Updates' repositories by default

• Fixed deprecation warning when thor encountered an error. Also, instead of returning 0 for thor errors, rmt-cli will return 1 instead.

• Version 2.5.13

• Added rmt-cli repos clean command to remove locally mirrored files of repositories which are not marked to be mirrored.

• Previously, RMT didn't track…

This update for rmt-server fixes the following issues:

• 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.

• Version 2.6.4

• 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.

• Version 2.6.3

• Instead of using an MD5 of URLs for custom repository friendly_ids, RMT now builds an ID from the name.

• Version 2.6.2

• 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.

• Version 2.6.1

• Fixed an issue where relative paths supplied to rmt-cli import repos caused the command to fail.

• Version 2.6.0

• 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.

• Version 2.5.20

• Updated rails from 6.0.3.2 to 6.0.3.3:

  • actionview (CVE-2020-15169)

• Version 2.5.19

• RMT now has the ability to remove local systems with the command rmt-cli systems remove.

• Version 2.5.18

• Fixed exit code for rmt-cli mirror and its subcommands. Now it exits with 1 whenever an error occurs during mirroring

• Improved message logging for rtm-cli mirror. Instead of logging an error when it occurs, the command summarize all errors at the end of execution. Now log messages have colors to better identify failure/success.

• Version 2.5.17

• RMT no longer provides the installer updates repository to systems via its zypper service. This repository is used during the installation process, as it provides an up-to-date installation experience, but it has no use on an already installed system.

• Version 2.5.16

• Updated RMT's rails and puma dependencies.

  • puma (CVE-2020-11076, CVE-2020-11077, CVE-2020-5249, CVE-2020-5247 CVE-2019-16770)
  • actionpack (CVE-2020-8185, CVE-2020-8164, CVE-2020-8166)
  • actionview (CVE-2020-8167, CVE-2020-5267, CVE-2019-5418, CVE-2019-5419)
  • activesupport (CVE-2020-8165)
  • railties (CVE-2019-5420)

• Version 2.5.15

• RMT now checks if repositories are fully mirrored during the activation process. Previously, RMT only checked if the repositories were enabled to be mirrored, but not that they were actually mirrored. In this case, RMTs were not able to provide the repository data which systems assumed it had.

• Version 2.5.14

• Enable 'Installer-Updates' repositories by default

• Fixed deprecation warning when thor encountered an error. Also, instead of returning 0 for thor errors, rmt-cli will return 1 instead.

• Version 2.5.13

• Added rmt-cli repos clean command to remove locally mirrored files of repositories which are not marked to be mirrored.

• Previously, RMT didn't track…

This update for rubygem-rack fixes the following issues:

• CVE-2020-8184: Fixed vulnerability where percent-encoded cookies can be used to overwrite existing prefixed cookie names (bsc#1173351).
• CVE-2020-8161: Fixed directory traversal in Rack:Directory (bsc#1172037).

It was discovered that Rack incorrectly handled certain paths. An attacker could possibly use this issue to obtain sensitive information. (CVE-2020-8161)

It was discovered that Rack incorrectly validated cookies. An attacker could possibly use this issue to forge a secure cookie. (CVE-2020-8184)

USN-4561-1 fixed vulnerabilities in Rack. This update provides the corresponding update for Ubuntu 16.04 LTS, Ubuntu 20.04 LTS and Ubuntu 20.10.

Original advisory details:

It was discovered that Rack incorrectly handled certain paths. An attacker could possibly use this issue to obtain sensitive information. This issue only affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. (CVE-2020-8161)

It was discovered that Rack incorrectly validated cookies. An attacker could possibly use this issue to forge a secure cookie. (CVE-2020-8184)

It was discovered that Rack insecurely handled session ids. An unauthenticated remote attacker could possibly use this issue to perform a timing attack and hijack sessions. (CVE-2019-16782)

It was discovered that Rack was incorrectly handling cookies during parsing, not validating them or performing the necessary integrity checks. An attacker could possibly use this issue to overwrite existing cookie data and gain control over a remote system's behaviour. This issue only affected Ubuntu 14.04 ESM. (CVE-2020-8184)

It was discovered that Rack was not properly parsing data when processing multipart POST requests. If a user or automated system were tricked into sending a specially crafted multipart POST request to an application using Rack, a remote attacker could possibly use this issue to cause a denial of service. This issue was only fixed in Ubuntu 14.04 ESM and Ubuntu 16.04 ESM. (CVE-2022-30122)

It was discovered that Rack was not properly escaping untrusted data when performing logging operations, which could cause shell escaped sequences to be written to a terminal. If a user or automated system were tricked into sending a specially crafted request to an application using Rack, a remote attacker could possibly use this issue to execute arbitrary code in the machine running the application. This issue was only fixed in Ubuntu 14.04 ESM and Ubuntu 16.04 ESM. (CVE-2022-30123)