Loading vulnerability…
CVE-2018-11218 is a memory corruption vulnerability in the cmsgpack library used by the Lua subsystem in Redis. Affected versions are Redis before 3.2.12, 4.x before 4.0.10, and 5.x before 5.0 RC2. The issue is caused by stack-based buffer overflows during processing within the cmsgpack component, which can corrupt memory and destabilize the Redis process.
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 contains a single Metasploit module: 'Redis Replication Code Execution' (modules/exploits/linux/redis/redis_replication_cmd_exec.rb). The module exploits CVE-2018-11218, targeting Redis servers (version 4.x and 5.x) running on Linux. It abuses the Redis replication feature to load a malicious module (shared object file) onto the target, enabling arbitrary code execution. The exploit sets up a rogue Redis master server, has the target connect as a slave, and delivers the payload via the replication protocol. The default payload is a Meterpreter reverse shell, but custom payloads can be compiled and delivered. The module requires network access to the target's Redis service (default port 6379) and the ability to execute CONFIG commands. The exploit is weaponized, allowing for flexible payload delivery and post-exploitation capabilities. The only file in the repository is a Ruby script designed for use within the Metasploit framework.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.