CVE-2020-8165 is an unsafe deserialization vulnerability in ActiveSupport's MemCacheStore and RedisCacheStore. In affected Rails releases, attacker-controlled data written to a cache with the raw option enabled can subsequently be interpreted and unmarshalled as a Ruby object when it is read using incompatible cache serialization settings. This permits injection of untrusted Ruby objects into the application process and can result in remote code execution depending on available deserialization gadget chains.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept exploit for CVE-2020-8165, a remote code execution vulnerability in Ruby on Rails (version 5.2.3) when using Redis as the cache store. The exploit leverages unsafe deserialization via a crafted payload sent to the /users endpoint, which is handled by the UsersController#index action. The payload is a marshaled Ruby object that, when deserialized by the vulnerable cache fetch operation, results in arbitrary command execution on the server (demonstrated by creating /tmp/rce). The repository is structured as a minimal Rails API application, with the main exploit logic described in the README and implemented in the controller. The exploit requires the target to be running the vulnerable Rails version, have Redis configured as the cache store, and expose the /users endpoint. No detection or fake code is present; this is a working exploit POC.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.