Rest ClientApplication · Rest Client Project
CVE-2019-15224
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe rest-client Ruby gem versions 1.6.10 through 1.6.13, as distributed on RubyGems.org, were compromised by a third party who inserted malicious code providing arbitrary code-execution capability. This represents a supply chain compromise where the gem itself contains a backdoor.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Rest ClientApplication
>= 1.6.10, <= 1.6.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
List installed rest-client gem versionRun `gem list rest-client` or check the Gemfile.lock file for the rest-client entryAffected if The version shown is 1.6.10, 1.6.11, 1.6.12, or 1.6.13
-
Verify exact gem versionRun `gem specification rest-client` and look for the version: field, or run a Ruby script with `require 'rest-client'; puts RestClient::VERSION`Affected if The version is >= 1.6.10 and <= 1.6.13
-
Check application dependency filesReview Gemfile.lock in the project root and search for the rest-client lineAffected if The version listed for rest-client is any version between 1.6.10 and 1.6.13 inclusive
If the installed rest-client gem version is 1.6.10, 1.6.11, 1.6.12, or 1.6.13, the environment contains the compromised gem and is affected by this supply chain attack.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImmediately upgrade to rest-client version 1.6.14 or later, or uninstall the affected gem versions if upgrading is not feasible. Audit systems for any unauthorized access since the compromised versions were available.
rest-client gem >= 1.6.14 (preferably latest stable version)
- Check current rest-client gem version in your project (gem list rest-client)
- If version is between 1.6.10 and 1.6.13 inclusive, the gem is compromised and must be upgraded immediately
- Run 'gem update rest-client' or update the version in your Gemfile to a version >= 1.6.14
- Run 'bundle install' to update dependencies
- Verify the new version is installed: gem list rest-client
- Audit your application for any unauthorized code execution or data exfiltration that may have occurred while the compromised version was in use
- Consider rotating credentials and keys if the compromised version was deployed to production
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rest Client
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15224 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data