Summary
Package updates are available for Amazon Linux 2 that fix the following vulnerabilities: CVE-2019-8325: An issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::CommandManager#run calls alert_error without escaping, escape sequence injection is possible. (There are many ways to cause an error.) 1692522: CVE-2019-8325 rubygems: Escape sequence injection vulnerability in errors CVE-2019-8324: An issue was discovered in RubyGems 2.6 and later through 3.0.2. A crafted gem with a multi-line name is not handled correctly. Therefore, an attacker could inject arbitrary code to the stub line of gemspec, which is eval-ed by code in ensure_loadable_spec during the preinstall check. 1692520: CVE-2019-8324 rubygems: Installing a malicious gem may lead to arbitrary code execution CVE-2019-8323: An issue was discovered in RubyGems 2.6 and later through 3.0.2. Gem::GemcutterUtilities#with_response may output the API response to stdout as it is. Therefore, if the API side modifies the response, escape sequence injection may occur. 1692519: CVE-2019-8323 rubygems: Escape sequence injection vulnerability in API response handling CVE-2019-8322: An issue was discovered in RubyGems 2.6 and later through 3.0.2. The gem owner command outputs the contents of the API response directly to stdout. Therefore, if the response is crafted, escape sequence injection may occur. 1692516: CVE-2019-8322 rubygems: Escape sequence injection vulnerability in gem owner
Fixed packages 16
| Release | Package | Fixed in |
|---|---|---|
| Amazon Linux · 2 | ruby | 0:2.0.0.648-35.amzn2.0.1 |
| Amazon Linux · 2 | ruby-debuginfo | 0:2.0.0.648-35.amzn2.0.1 |
| Amazon Linux · 2 | ruby-devel | 0:2.0.0.648-35.amzn2.0.1 |
| Amazon Linux · 2 | ruby-doc | 0:2.0.0.648-35.amzn2.0.1 |
| Amazon Linux · 2 | ruby-irb | 0:2.0.0.648-35.amzn2.0.1 |
| Amazon Linux · 2 | ruby-libs | 0:2.0.0.648-35.amzn2.0.1 |
| Amazon Linux · 2 | ruby-tcltk | 0:2.0.0.648-35.amzn2.0.1 |
| Amazon Linux · 2 | rubygem-bigdecimal | 0:1.2.0-35.amzn2.0.1 |
| Amazon Linux · 2 | rubygem-io-console | 0:0.4.2-35.amzn2.0.1 |
| Amazon Linux · 2 | rubygem-json | 0:1.7.7-35.amzn2.0.1 |
| Amazon Linux · 2 | rubygem-minitest | 0:4.3.2-35.amzn2.0.1 |
| Amazon Linux · 2 | rubygem-psych | 0:2.0.0-35.amzn2.0.1 |
| Amazon Linux · 2 | rubygem-rake | 0:0.9.6-35.amzn2.0.1 |
| Amazon Linux · 2 | rubygem-rdoc | 0:4.0.0-35.amzn2.0.1 |
| Amazon Linux · 2 | rubygems | 0:2.0.14.1-35.amzn2.0.1 |
| Amazon Linux · 2 | rubygems-devel | 0:2.0.14.1-35.amzn2.0.1 |
Vulnerabilities 4
-
High 8.8
Code injection in RubyGems
An issue was discovered in RubyGems 2.6 and later through 3.0.2. A crafted gem with a multi-line name is not handled correctly. Therefore, an attacker could inject arbitrary code to the stub line of gemspec, which is eval-ed by code in ensure_loadable_spec du…
-
High 7.5
RubyGems Escape sequence injection vulnerability in gem owner
An issue was discovered in RubyGems 2.6 and later through 3.0.2. The gem owner command outputs the contents of the API response directly to stdout. Therefore, if the response is crafted, escape sequence injection may occur.
-
High 7.5
RubyGems Escape sequence injection vulnerability in api response handling
An issue was discovered in RubyGems 2.6 and later through 3.0.2. Gem::GemcutterUtilities#with_response may output the API response to stdout as it is. Therefore, if the API side modifies the response, escape sequence injection may occur.
-
High 7.5
RubyGems Escape sequence injection in errors
An issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::CommandManager#run calls alert_error without escaping, escape sequence injection is possible. (There are many ways to cause an error.)