# CVE-2019-15224: rest-client Gem Contains Malicious Code > A backdoor in the rest-client gem allows attackers to execute arbitrary code on systems using affected versions. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed - **Fix available:** Yes - **Published:** 19 Aug 2019 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-333g-rpr4-7hxq ## What is CVE-2019-15224? CVE-2019-15224 is a critical code injection vulnerability in n/a, published on 19 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The rest-client gem 1.6.10 through 1.6.13 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party. Versions <=1.6.9 and >=1.6.14 are unaffected. Weakness: CWE-94 (Improper Control of Generation of Code) ## Which versions are affected by CVE-2019-15224? 22 open source packages ship an affected version, including cron_parser, awesome-bot and bitcoin_vanity. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `cron_parser` | RubyGems | All versions | None | | `cron_parser` | RubyGems | All versions | None | | `cron_parser` | RubyGems | From 1.0.13 to 1.0.14 | None | | `cron_parser` | RubyGems | From 1.0.13 to 1.0.14 | None | | `awesome-bot` | RubyGems | All versions | None | | `awesome-bot` | RubyGems | All versions | None | | `bitcoin_vanity` | RubyGems | All versions | None | | `bitcoin_vanity` | RubyGems | All versions | None | | `blockchain_wallet` | RubyGems | All versions | None | | `blockchain_wallet` | RubyGems | All versions | None | | `capistrano-colors` | RubyGems | All versions | None | | `capistrano-colors` | RubyGems | All versions | None | | `coin_base` | RubyGems | All versions | None | | `coin_base` | RubyGems | All versions | None | | `coming-soon` | RubyGems | All versions | None | | `coming-soon` | RubyGems | All versions | None | | `doge-coin` | RubyGems | All versions | None | | `doge-coin` | RubyGems | All versions | None | | `omniauth_amazon` | RubyGems | All versions | None | | `omniauth_amazon` | RubyGems | All versions | None | | `rest-client` | RubyGems | From 1.6.10 | 1.7.0 | | `rest-client` | RubyGems | From 1.6.10 | 1.7.0 | Products: Rest-Client Project Rest-Client. ## How do I fix CVE-2019-15224? Upgrade to a fixed version. ## Is CVE-2019-15224 being exploited? There is no known exploitation of CVE-2019-15224 in the wild and no public exploit code. Public exploit code: - Example InSpec profile to detect presence of a malicious rest-client gem (CVE-2019-15224) (github_poc): https://github.com/chef-cft/inspec_cve_2019_15224 ## Other vulnerabilities in n/a - [CVE-2015-1820](https://insights.sbomify.com/CVE-2015-1820/): rest-client Gem Vulnerable to Session Fixation (critical 9.8) - [CVE-2015-3448](https://insights.sbomify.com/CVE-2015-3448/): rest-client allows local users to obtain sensitive information by reading the log (low 2.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-15224 and fix it if it is affected. What it is: CVE-2019-15224 is a critical code injection vulnerability in n/a, published on 19 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-15224 in the wild and no public exploit code. Affected packages and fixed versions: - cron_parser (RubyGems): affected all versions; no fix listed - cron_parser (RubyGems): affected all versions; no fix listed - cron_parser (RubyGems): affected from 1.0.13 up to 1.0.14; no fix listed - cron_parser (RubyGems): affected from 1.0.13 up to 1.0.14; no fix listed - awesome-bot (RubyGems): affected all versions; no fix listed - awesome-bot (RubyGems): affected all versions; no fix listed - bitcoin_vanity (RubyGems): affected all versions; no fix listed - bitcoin_vanity (RubyGems): affected all versions; no fix listed - blockchain_wallet (RubyGems): affected all versions; no fix listed - blockchain_wallet (RubyGems): affected all versions; no fix listed - capistrano-colors (RubyGems): affected all versions; no fix listed - capistrano-colors (RubyGems): affected all versions; no fix listed 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-15224/ (Markdown: https://insights.sbomify.com/CVE-2019-15224/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-15224 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-15224 - OSV: https://osv.dev/vulnerability/CVE-2019-15224 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-15224/ Summaries are generated and may contain mistakes; the official description above is the record.