CVE-2020-15169

There is a potential Cross-Site Scripting (XSS) vulnerability in Action View's translation helpers. Views that allow the user to control the default (not found) value of the t and translate helpers could be susceptible to XSS attacks.

Impact

When an HTML-unsafe string is passed as the default for a missing translation key named html or ending in _html, the default string is incorrectly marked as HTML-safe and not escaped. Vulnerable code may look like the following examples:

<%# The welcome_html translation is not defined for the current locale: %>
<%= t("welcome_html", default: untrusted_user_controlled_string) %>

<%# Neither the title.html translation nor the missing.html translation is defined for the current locale: %>
<%= t("title.html", default: [:"missing.html", untrusted_user_controlled_string]) %>

Patches

Patched Rails versions, 6.0.3.3 and 5.2.4.4, are available from the normal locations.

The patches have also been applied to the master, 6-0-stable, and 5-2-stable branches on GitHub. If you track any of these branches, you should update to the latest.

To aid users who aren’t able to upgrade immediately, we’ve provided patches for the two supported release series. They are in git-am format and consist of a single changeset.

• 5-2-translate-helper-xss.patch — patch for the 5.2 release series
• 6-0-translate-helper-xss.patch — patch for the 6.0 release series

Please note that only the 5.2 and 6.0 release series are currently supported. Users of earlier, unsupported releases are advised to update as soon as possible, as we cannot provide security fixes for unsupported releases.

Workarounds

Impacted users who can’t upgrade to a patched Rails version can avoid this issue by manually escaping default translations with the html_escape helper (aliased as h):

<%= t("welcome_html", default: h(untrusted_user_controlled_string)) %>

Simple, battle-tested conventions and helpers for building web pages.

Security Fix(es):

In Action View before versions 5.2.4.4 and 6.0.3.3 there is a potential Cross-Site Scripting (XSS) vulnerability in Action View s translation helpers. Views that allow the user to control the default (not found) value of the t and translate helpers could be susceptible to XSS attacks. When an HTML-unsafe string is passed as the default for a missing translation key named html or ending in _html, the default string is incorrectly marked as HTML-safe and not escaped. This is patched in versions 6.0.3.3 and 5.2.4.4. A workaround without upgrading is proposed in the source advisory.(CVE-2020-15169)

In Action View before versions 5.2.4.4 and 6.0.3.3 there is a potential Cross-Site Scripting (XSS) vulnerability in Action View's translation helpers. Views that allow the user to control the default (not found) value of the t and translate helpers could be susceptible to XSS attacks. When an HTML-unsafe string is passed as the default for a missing translation key named html or ending in _html, the default string is incorrectly marked as HTML-safe and not escaped. This is patched in versions 6.0.3.3 and 5.2.4.4. A workaround without upgrading is proposed in the source advisory.

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-actionview-5.2-5.2.6-1.2 package on the GA media of openSUSE Tumbleweed.

This update for rubygem-actionview-4_2 fixes the following issues:

• CVE-2020-15169: Fix cross-site scripting in translation helpers (bsc#1176421)

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-actionview-5_1 fixes the following issues:

• CVE-2022-27777: Fixed possible cross-site scripting vulnerability in Action View tag helpers (bsc#1199060).
• CVE-2020-15169: Fixed cross-site scripting in translation helpers (bsc#1176421).
• CVE-2020-8167: Fixed CSRF vulnerability in rails-ujs (bsc#1172184).