CVE-2024-55656 is an integer overflow vulnerability in RedisBloom, a Redis module that provides probabilistic data structures. The flaw is in handling the CMS.INITBYDIM command, which initializes a Count-Min Sketch using user-supplied width and depth values. These parameters are used by NewCMSketch() to calculate the required heap allocation. Due to integer wraparound during this size calculation, the module can allocate less memory than required. Subsequent operations on the undersized allocation can then perform out-of-bounds reads and writes, resulting in information disclosure and memory corruption.
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 working exploit for CVE-2024-55656, an integer overflow vulnerability in the RedisBloom module (v2.6.12) shipped with Redis Stack 7.2.0-v10. The exploit is implemented in Python (exploit/exploit.py) and leverages the pwn library to interact with a vulnerable Redis server over the network. The attack works by abusing the CMS.INITBYDIM command to trigger an integer overflow, allowing the attacker to perform out-of-bounds (OOB) reads and writes via CMS.QUERY and CMS.INCRBY commands. These primitives are used to leak memory and overwrite function pointers, culminating in the execution of a ROP chain and shellcode that provides a reverse shell to the attacker's machine (as specified by --lhost and --lport). The exploit requires the attacker to have access to the Redis server (including authentication if enabled). The repository also includes a JSON file (murmurhash2_1024.json) used for crafting the necessary CMS commands, and a README.md with detailed usage instructions and vulnerability analysis. The exploit is operational and provides a real RCE payload, but is not part of a larger exploitation framework.
3 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.