7184 matches found
PT-2019-1027
Name of the Vulnerable Software and Affected Versions: RubyGems versions 2.6 through 3.0.2 Description: An issue in the Gem::GemcutterUtilities module of RubyGems may output the API response to stdout as it is, potentially leading to escape sequence injection if the API side modifies the response...
PT-2019-4617
Name of the Vulnerable Software and Affected Versions RubyGems versions 2.6 through 3.0.2 Description An issue in RubyGems allows an attacker to inject arbitrary code into the stub line of gemspec, which is eval-ed by code in ensure loadable spec during the preinstall check. This is due to...
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 ensureloadablespec during the preinstall check...
UBUNTU-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...
UBUNTU-CVE-2019-8320
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 malicious gem could...
UBUNTU-CVE-2019-8321
An issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::UserInteractionverbose calls say without escaping, escape sequence injection is possible...
UBUNTU-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 ensureloadablespec during the preinstall check...
CVE-2019-8325
An issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::CommandManagerrun calls alerterror without escaping, escape sequence injection is possible. There are many ways to cause an error...
PT-2019-1025
Name of the Vulnerable Software and Affected Versions: RubyGems versions 2.6 through 3.0.2 Description: The issue is related to insufficient escaping in the Gem::UserInteraction module of the RubyGems package management system. This allows a remote attacker to inject escape sequences, potentially...
PT-2019-1028
Name of the Vulnerable Software and Affected Versions: RubyGems versions 2.6 through 3.0.2 Description: The issue is related to insufficient escaping in the Gem::CommandManager module of the RubyGems package management system. This allows a remote attacker to inject escape sequences, potentially...
WPScan v3.4.5 - Black Box WordPress Vulnerability Scanner
WPScan is a free, for non-commercial use, black box WordPress vulnerability scanner written for security professionals and blog maintainers to test the security of their sites. INSTALL Prerequisites Optional but highly recommended: RVM Ruby = 2.3 - Recommended: latest Ruby 2.5.0 to 2.5.3 can caus...
FreeBSD : RubyGems -- multiple vulnerabilities (27b12d04-4722-11e9-8b7c-b5e01141761f)
RubyGems Security Advisories : CVE-2019-8320: Delete directory using symlink when decompressing tar CVE-2019-8321: Escape sequence injection vulnerability in 'verbose' CVE-2019-8322: Escape sequence injection vulnerability in 'gem owner' CVE-2019-8323: Escape sequence injection vulnerability in A...
RubyGems Code Execution Vulnerability (CNVD-2019-12147)
RubyGems is a Ruby package manager from the RubyGems organization. The product is mainly used for publishing and managing Ruby packages. A security vulnerability exists in RubyGems versions 2.6 through 3.0.2 in gem owner, which stems from the gem owner command exporting the contents of an API...
RubyGems Code Execution Vulnerability (CNVD-2019-12149)
RubyGems is a Ruby package manager from the RubyGems organization. The product is mainly used for publishing and managing Ruby packages. A security vulnerability exists in RubyGems versions 2.6 through 3.0.2, which stems from the program not properly handling gem with multiple lines in the name.A...
RubyGems Code Execution Vulnerability
RubyGems is a Ruby package manager from the RubyGems organization. The product is mainly used for publishing and managing Ruby packages. A security vulnerability exists in RubyGems versions 2.6 through 3.0.2, which stems from Gem::CommandManagerrun calling alerterror without escaping, and can be...
RubyGems Path Traversal Vulnerability
RubyGems is a Ruby package manager from the RubyGems organization. The product is mainly used for publishing and managing Ruby packages. A directory traversal vulnerability exists in RubyGems versions 2.7.6 through 3.0.2. An attacker can exploit this vulnerability to delete arbitrary files on a...
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...
Delete directory using symlink when decompressing tar
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 malicious gem could...
Installing a malicious gem may lead to arbitrary code execution
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 ensureloadablespec during the preinstall check...
Escape sequence injection vulnerability in api response handling
An issue was discovered in RubyGems 2.6 and later through 3.0.2. Gem::GemcutterUtilitieswithresponse may output the API response to stdout as it is. Therefore, if the API side modifies the response, escape sequence injection may occur...