CVE-2019-8324
published 2019-06-17CVE-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…
PriorityP346high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
3.22%
86.8th percentile
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.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | jruby | < jruby 9.1.17.0-3 (bookworm) | jruby 9.1.17.0-3 (bookworm) |
| debian | rubygems | < jruby 9.1.17.0-3 (bookworm) | jruby 9.1.17.0-3 (bookworm) |
| jruby | jruby | >= 0 < 9.1.17.0-3 | 9.1.17.0-3 |
| jruby | jruby | >= 0 < 9.1.17.0-3 | 9.1.17.0-3 |
| jruby | jruby | >= 0 < 9.1.17.0-3 | 9.1.17.0-3 |
| opensuse | leap | — | — |
| opensuse | leap | — | — |
| redhat | enterprise_linux | — | — |
| rubygems | rubygems | >= 0 < 3.2.0~rc.1-1 | 3.2.0~rc.1-1 |
| rubygems | rubygems | >= 0 < 3.2.0~rc.1-1 | 3.2.0~rc.1-1 |
| rubygems | rubygems | >= 0 < 3.2.0~rc.1-1 | 3.2.0~rc.1-1 |
| rubygems | rubygems | >= 0 < 3.2.0~rc.1-1 | 3.2.0~rc.1-1 |
| rubygems | rubygems | 2.6.0 – 3.0.2 | — |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
osv8.8HIGH
vendor_debian8.8HIGH
vendor_redhat8.8HIGH
vendor_ubuntu7.4HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
Ruby vulnerabilities
vendor_ubuntu·2019-04-11·CVSS 7.4
CVE-2019-8320 [HIGH] Ruby vulnerabilities
Title: Ruby vulnerabilities
Summary: Several security issues were fixed in Ruby.
It was discovered that Ruby incorrectly handled certain RubyGems.
An attacker could possibly use this issue to execute arbitrary commands.
(CVE-2019-8320)
It was discovered that Ruby incorrectly handled certain inputs.
An attacker could possibly use this issue to execute arbitrary code.
(CVE-2019-8321, CVE-2019-8322, CVE-2019-8323, CVE-2019-8324, CVE-2019-8325)
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
rubygems: Installing a malicious gem may lead to arbitrary code execution
vendor_redhat·2019-03-05·CVSS 8.8
CVE-2019-8324 [HIGH] CWE-20 rubygems: Installing a malicious gem may lead to arbitrary code execution
rubygems: 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 ensure_loadable_spec during the preinstall check.
A flaw was found in RubyGems. A crafted gem with a multi-line name is not handled correctly allowing an attacker to inject arbitrary code to the stub line of gemspec. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Package: rubygems (Red Hat Enterprise Linux 6) - Not affected
Package: rh-ruby26-ruby (Red Hat Software Collections) - Not affected
Debian
CVE-2019-8324: jruby - An issue was discovered in RubyGems 2.6 and later through 3.0.2. A crafted gem w...
vendor_debian·2019·CVSS 8.8
CVE-2019-8324 [HIGH] CVE-2019-8324: jruby - An issue was discovered in RubyGems 2.6 and later through 3.0.2. A crafted gem w...
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.
Scope: local
bookworm: resolved (fixed in 9.1.17.0-3)
forky: resolved (fixed in 9.1.17.0-3)
sid: resolved (fixed in 9.1.17.0-3)
trixie: resolved (fixed in 9.1.17.0-3)
OSV
Code injection in RubyGems
osv·2019-06-20
CVE-2019-8324 [HIGH] Code injection in RubyGems
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 during the preinstall check.
GHSA
Code injection in RubyGems
ghsa·2019-06-20
CVE-2019-8324 [HIGH] CWE-94 Code injection in RubyGems
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 during the preinstall check.
OSV
CVE-2019-8324: An issue was discovered in RubyGems 2
osv·2019-06-17·CVSS 8.8
CVE-2019-8324 [HIGH] CVE-2019-8324: An issue was discovered in RubyGems 2
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.
OSV
ruby1.9.1, ruby2.0, ruby2.3, ruby2.5 vulnerabilities
osv·2019-04-11·CVSS 7.4
CVE-2019-8320 [HIGH] ruby1.9.1, ruby2.0, ruby2.3, ruby2.5 vulnerabilities
ruby1.9.1, ruby2.0, ruby2.3, ruby2.5 vulnerabilities
It was discovered that Ruby incorrectly handled certain RubyGems.
An attacker could possibly use this issue to execute arbitrary commands.
(CVE-2019-8320)
It was discovered that Ruby incorrectly handled certain inputs.
An attacker could possibly use this issue to execute arbitrary code.
(CVE-2019-8321, CVE-2019-8322, CVE-2019-8323, CVE-2019-8324, CVE-2019-8325)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-8324 rubygems: Installing a malicious gem may lead to arbitrary code execution
bugzilla·2019-03-25·CVSS 8.8
CVE-2019-8324 [HIGH] CVE-2019-8324 rubygems: Installing a malicious gem may lead to arbitrary code execution
CVE-2019-8324 rubygems: 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 ensure_loadable_spec during the preinstall check.
Upstream patch:
https://bugs.ruby-lang.org/attachments/7669
References:
https://www.ruby-lang.org/en/news/2019/03/05/multiple-vulnerabilities-in-rubygems/
https://blog.rubygems.org/2019/03/05/security-advisories-2019-03.html
Discussion:
Created rubygems tracking bugs for this issue:
Affects: fedora-all [bug 1692530]
---
The changeset in lib/rubygems/installer.rb has the fix for this. See the addition of verify_sp
Bugzilla
CVE-2019-8320 CVE-2019-8321 CVE-2019-8322 CVE-2019-8323 CVE-2019-8324 CVE-2019-8325 rubygems: various flaws [fedora-all]
bugzilla·2019-03-25·CVSS 7.4
CVE-2019-8320 [HIGH] CVE-2019-8320 CVE-2019-8321 CVE-2019-8322 CVE-2019-8323 CVE-2019-8324 CVE-2019-8325 rubygems: various flaws [fedora-all]
CVE-2019-8320 CVE-2019-8321 CVE-2019-8322 CVE-2019-8323 CVE-2019-8324 CVE-2019-8325 rubygems: various flaws [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: thi
http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00036.htmlhttps://access.redhat.com/errata/RHSA-2019:1972https://hackerone.com/reports/328571https://lists.debian.org/debian-lts-announce/2020/08/msg00027.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-07/msg00036.htmlhttps://access.redhat.com/errata/RHSA-2019:1972https://hackerone.com/reports/328571https://lists.debian.org/debian-lts-announce/2020/08/msg00027.html
2019-06-17
Published