# CVE-2019-8324: Code injection in RubyGems > Attackers can execute arbitrary code by crafting a gem with a multi-line name, exploiting improper handling in RubyGems during preinstall checks. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 17 Jun 2019 - **Updated:** 4 Aug 2024 - **Also known as:** ALPINE-CVE-2019-8324, ALSA-2019:1972, DEBIAN-CVE-2019-8324, GHSA-76wm-422q-92mq, RHSA-2019:1151, RHSA-2019:1972, RLSA-2019:1972, UBUNTU-CVE-2019-8324 ## What is CVE-2019-8324? CVE-2019-8324 is a high-severity code injection vulnerability in Debian Debian Linux, published on 17 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-94 (Improper Control of Generation of Code) ## Which versions are affected by CVE-2019-8324? 4 open source packages ship an affected version, including rubygems-update. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `rubygems-update` | RubyGems | From 2.6.0 | 2.7.9 | | `rubygems-update` | RubyGems | From 2.6.0 | 2.7.9 | | `rubygems-update` | RubyGems | From 3.0.0 | 3.0.2 | | `rubygems-update` | RubyGems | From 3.0.0 | 3.0.2 | | `rubygem-abrt` | AlmaLinux:8 | All versions | 0.3.0-4.module_el8.5.0+259+8cec6917 | | `rubygem-abrt` | AlmaLinux:8 | All versions | 0.3.0-4.module_el8.5.0+2623+08a8ba32 | | `rubygem-abrt-doc` | AlmaLinux:8 | All versions | 0.3.0-4.module_el8.5.0+259+8cec6917 | | `rubygem-abrt-doc` | AlmaLinux:8 | All versions | 0.3.0-4.module_el8.5.0+2623+08a8ba32 | | `rubygem-bson` | AlmaLinux:8 | All versions | 4.3.0-2.module_el8.5.0+259+8cec6917 | | `rubygem-bson` | AlmaLinux:8 | All versions | 4.3.0-2.module_el8.5.0+2625+ec418553 | | `rubygem-bson-doc` | AlmaLinux:8 | All versions | 4.3.0-2.module_el8.5.0+259+8cec6917 | | `rubygem-bson-doc` | AlmaLinux:8 | All versions | 4.3.0-2.module_el8.5.0+2625+ec418553 | | `rubygem-mongo` | AlmaLinux:8 | All versions | 2.5.1-2.module_el8.5.0+259+8cec6917 | | `rubygem-mongo` | AlmaLinux:8 | All versions | 2.5.1-2.module_el8.5.0+2625+ec418553 | | `rubygem-mongo-doc` | AlmaLinux:8 | All versions | 2.5.1-2.module_el8.5.0+259+8cec6917 | | `rubygem-mongo-doc` | AlmaLinux:8 | All versions | 2.5.1-2.module_el8.5.0+2625+ec418553 | | `rubygem-mysql2` | AlmaLinux:8 | All versions | 0.4.10-4.module_el8.5.0+259+8cec6917 | | `rubygem-mysql2` | AlmaLinux:8 | All versions | 0.4.10-4.module_el8.5.0+2625+ec418553 | | `rubygem-mysql2-doc` | AlmaLinux:8 | All versions | 0.4.10-4.module_el8.5.0+259+8cec6917 | | `rubygem-mysql2-doc` | AlmaLinux:8 | All versions | 0.4.10-4.module_el8.5.0+2625+ec418553 | | `rubygem-pg` | AlmaLinux:8 | All versions | 1.0.0-2.module_el8.5.0+259+8cec6917 | | `rubygem-pg` | AlmaLinux:8 | All versions | 1.0.0-2.module_el8.5.0+2625+ec418553 | | `rubygem-pg-doc` | AlmaLinux:8 | All versions | 1.0.0-2.module_el8.5.0+259+8cec6917 | | `rubygem-pg-doc` | AlmaLinux:8 | All versions | 1.0.0-2.module_el8.5.0+2625+ec418553 | | `ruby` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.5.3-104.module+el8.0.0+3250+4b7d6d43 | | `ruby-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.5.3-104.module+el8.0.0+3250+4b7d6d43 | | `ruby-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.5.3-104.module+el8.0.0+3250+4b7d6d43 | | `ruby-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.5.3-104.module+el8.0.0+3250+4b7d6d43 | | `ruby-doc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.5.3-104.module+el8.0.0+3250+4b7d6d43 | | `ruby-irb` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.5.3-104.module+el8.0.0+3250+4b7d6d43 | | `ruby-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.5.3-104.module+el8.0.0+3250+4b7d6d43 | | `ruby-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.5.3-104.module+el8.0.0+3250+4b7d6d43 | | `rubygem-abrt` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.3.0-4.module+el8.0.0+3250+4b7d6d43 | | `rubygem-abrt-doc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.3.0-4.module+el8.0.0+3250+4b7d6d43 | | `rubygem-bigdecimal` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.4-104.module+el8.0.0+3250+4b7d6d43 | | `rubygem-bigdecimal-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.4-104.module+el8.0.0+3250+4b7d6d43 | | `rubygem-bson` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.3.0-2.module+el8.0.0+3250+4b7d6d43 | | `rubygem-bson-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.3.0-2.module+el8.0.0+3250+4b7d6d43 | | `rubygem-bson-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.3.0-2.module+el8.0.0+3250+4b7d6d43 | | `rubygem-bson-doc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.3.0-2.module+el8.0.0+3250+4b7d6d43 | Products: Debian Debian Linux, Opensuse Leap, Redhat Enterprise Linux, Rubygems Rubygems. ## How do I fix CVE-2019-8324? Upgrade rubygems-update to a fixed version for your release line: 2.7.9 or 3.0.2. ## Is CVE-2019-8324 being exploited? There is no known exploitation of CVE-2019-8324 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-8324 and fix it if it is affected. What it is: CVE-2019-8324 is a high-severity code injection vulnerability in Debian Debian Linux, published on 17 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-8324 in the wild and no public exploit code. Affected packages and fixed versions: - rubygems-update (RubyGems): affected from 2.6.0; fixed in 2.7.9 - rubygems-update (RubyGems): affected from 2.6.0; fixed in 2.7.9 - rubygems-update (RubyGems): affected from 3.0.0; fixed in 3.0.2 - rubygems-update (RubyGems): affected from 3.0.0; fixed in 3.0.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-8324/ (Markdown: https://insights.sbomify.com/CVE-2019-8324/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-8324 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-8324 - OSV: https://osv.dev/vulnerability/CVE-2019-8324 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-8324/ Summaries are generated and may contain mistakes; the official description above is the record.