rpm package
almalinux/rubygem-abrt-doc
pkg:rpm/almalinux/rubygem-abrt-doc
Vulnerabilities (57)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2020-36327 | Hig | 8.8 | < 0.4.0-1.module_el8.5.0+118+1ab773e1 | 0.4.0-1.module_el8.5.0+118+1ab773e1 | Apr 29, 2021 | Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.16 sometimes chooses a dependency source based on the highest gem version number, which means that a rogue gem found at a public source may be chosen, even if the intended choice was a private gem that is a dependency of another | |
| CVE-2021-28965 | Hig | 7.5 | < 0.4.0-1.module_el8.5.0+118+1ab773e1 | 0.4.0-1.module_el8.5.0+118+1ab773e1 | Apr 21, 2021 | The REXML gem before 3.2.5 in Ruby before 2.6.7, 2.7.x before 2.7.3, and 3.x before 3.0.1 does not properly address XML round-trip issues. An incorrect document can be produced after parsing and serializing. | |
| CVE-2020-25613 | Hig | 7.5 | < 0.4.0-1.module_el8.5.0+118+1ab773e1 | 0.4.0-1.module_el8.5.0+118+1ab773e1 | Oct 6, 2020 | An issue was discovered in Ruby through 2.5.8, 2.6.x through 2.6.6, and 2.7.x through 2.7.1. WEBrick, a simple HTTP server bundled with Ruby, had not checked the transfer-encoding header value rigorously. An attacker may potentially exploit this issue to bypass a reverse proxy (w | |
| CVE-2019-3881 | Hig | 7.8 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Sep 4, 2020 | Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an a | |
| CVE-2020-10933 | Med | 5.3 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | May 4, 2020 | An issue was discovered in Ruby 2.5.x through 2.5.7, 2.6.x through 2.6.5, and 2.7.0. If a victim calls BasicSocket#read_nonblock(requested_size, buffer, exception: false), the method resizes the buffer to fit the requested size, but no data is copied. Thus, the buffer string prov | |
| CVE-2020-10663 | Hig | 7.5 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Apr 28, 2020 | The JSON gem through 2.2.0 for Ruby, as used in Ruby 2.4 through 2.4.9, 2.5 through 2.5.7, and 2.6 through 2.6.5, has an Unsafe Object Creation Vulnerability. This is quite similar to CVE-2013-0269, but does not rely on poor garbage-collection behavior within Ruby. Specifically, | |
| CVE-2019-16255 | Hig | 8.1 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Nov 26, 2019 | Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 allows code injection if the first argument (aka the "command" argument) to Shell#[] or Shell#test in lib/shell.rb is untrusted data. An attacker can exploit this to call an arbitrary Ruby method. | |
| CVE-2019-16254 | Med | 5.3 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Nov 26, 2019 | Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 allows HTTP Response Splitting. If a program using WEBrick inserts untrusted input into the response header, an attacker can exploit it to insert a newline character to split a header, and inject malicious content t | |
| CVE-2019-16201 | Hig | 7.5 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Nov 26, 2019 | WEBrick::HTTPAuth::DigestAuth in Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 has a regular expression Denial of Service cause by looping/backtracking. A victim must expose a WEBrick server that uses DigestAuth to the Internet or a untrusted network. | |
| CVE-2019-15845 | Med | 6.5 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Nov 26, 2019 | Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 mishandles path checking within File.fnmatch functions. | |
| CVE-2019-19012 | Cri | 9.8 | < 0.3.0-4.module_el8.10.0+3871+342e2c2f | 0.3.0-4.module_el8.10.0+3871+342e2c2f | Nov 17, 2019 | An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a d | |
| CVE-2019-8323 | Hig | 7.5 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Jun 17, 2019 | 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. | |
| CVE-2019-8322 | Hig | 7.5 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Jun 17, 2019 | 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. | |
| CVE-2019-8321 | Hig | 7.5 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Jun 17, 2019 | An issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::UserInteraction#verbose calls say without escaping, escape sequence injection is possible. | |
| CVE-2019-8325 | Hig | 7.5 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Jun 17, 2019 | 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.) | |
| CVE-2019-8324 | Hig | 8.8 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Jun 17, 2019 | 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 c | |
| CVE-2019-8320 | Hig | 7.4 | < 0.3.0-4.module_el8.5.0+259+8cec6917 | 0.3.0-4.module_el8.5.0+259+8cec6917 | Jun 6, 2019 | A Directory Traversal issue was discovered in RubyGems 2.7.6 and later through 3.0.2. Before making new directories or touching files (which now include path-checking code for symlinks), it would delete the target destination. If that destination was hidden behind a symlink, a ma |
- affected < 0.4.0-1.module_el8.5.0+118+1ab773e1fixed 0.4.0-1.module_el8.5.0+118+1ab773e1
Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.16 sometimes chooses a dependency source based on the highest gem version number, which means that a rogue gem found at a public source may be chosen, even if the intended choice was a private gem that is a dependency of another
- affected < 0.4.0-1.module_el8.5.0+118+1ab773e1fixed 0.4.0-1.module_el8.5.0+118+1ab773e1
The REXML gem before 3.2.5 in Ruby before 2.6.7, 2.7.x before 2.7.3, and 3.x before 3.0.1 does not properly address XML round-trip issues. An incorrect document can be produced after parsing and serializing.
- affected < 0.4.0-1.module_el8.5.0+118+1ab773e1fixed 0.4.0-1.module_el8.5.0+118+1ab773e1
An issue was discovered in Ruby through 2.5.8, 2.6.x through 2.6.6, and 2.7.x through 2.7.1. WEBrick, a simple HTTP server bundled with Ruby, had not checked the transfer-encoding header value rigorously. An attacker may potentially exploit this issue to bypass a reverse proxy (w
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an a
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
An issue was discovered in Ruby 2.5.x through 2.5.7, 2.6.x through 2.6.5, and 2.7.0. If a victim calls BasicSocket#read_nonblock(requested_size, buffer, exception: false), the method resizes the buffer to fit the requested size, but no data is copied. Thus, the buffer string prov
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
The JSON gem through 2.2.0 for Ruby, as used in Ruby 2.4 through 2.4.9, 2.5 through 2.5.7, and 2.6 through 2.6.5, has an Unsafe Object Creation Vulnerability. This is quite similar to CVE-2013-0269, but does not rely on poor garbage-collection behavior within Ruby. Specifically,
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 allows code injection if the first argument (aka the "command" argument) to Shell#[] or Shell#test in lib/shell.rb is untrusted data. An attacker can exploit this to call an arbitrary Ruby method.
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 allows HTTP Response Splitting. If a program using WEBrick inserts untrusted input into the response header, an attacker can exploit it to insert a newline character to split a header, and inject malicious content t
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
WEBrick::HTTPAuth::DigestAuth in Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 has a regular expression Denial of Service cause by looping/backtracking. A victim must expose a WEBrick server that uses DigestAuth to the Internet or a untrusted network.
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 mishandles path checking within File.fnmatch functions.
- affected < 0.3.0-4.module_el8.10.0+3871+342e2c2ffixed 0.3.0-4.module_el8.10.0+3871+342e2c2f
An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a d
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
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.
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
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.
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
An issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::UserInteraction#verbose calls say without escaping, escape sequence injection is possible.
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
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.)
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
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 c
- affected < 0.3.0-4.module_el8.5.0+259+8cec6917fixed 0.3.0-4.module_el8.5.0+259+8cec6917
A Directory Traversal issue was discovered in RubyGems 2.7.6 and later through 3.0.2. Before making new directories or touching files (which now include path-checking code for symlinks), it would delete the target destination. If that destination was hidden behind a symlink, a ma
Page 3 of 3