dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2024-55656

HIGH · 8.8 CVSS v3.1 Published 2025-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
RedisBloom adds a set of probabilistic data structures to Redis. There is an integer overflow vulnerability in RedisBloom, which is a module used in Redis. The integer overflow vulnerability allows an attacker (a redis client which knows the password) to allocate memory in the heap lesser than the required memory due to wraparound. Then read and write can be performed beyond this allocated memory, leading to info leak and OOB write. The integer overflow is in CMS.INITBYDIM command, which initialize a Count-Min Sketch to dimensions specified by user. It accepts two values (width and depth) and uses them to allocate memory in NewCMSketch(). This vulnerability is fixed in 2.2.19, 2.4.12, 2.6.14, and 2.8.2.

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 confidence

Integer overflow in RedisBloom's CMS.INITBYDIM command allows authenticated Redis clients to cause undersized heap allocation via width/depth parameter wraparound, leading to out-of-bounds read/write and potential information disclosure.

MitigationUpgrade RedisBloom to version 2.2.19, 2.4.12, 2.6.14, or 2.8.2 or later. If immediate upgrade is not possible, restrict Redis access to trusted clients only since valid authentication credentials are required for exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm RedisBloom module is loaded
    Run the command 'MODULE LIST' in redis-cli to see if the bloom module is present. Look for module name containing 'bloom' or 'cms'.
    Affected if The bloom module appears in the output, indicating RedisBloom is active.
  2. Identify RedisBloom version
    Run 'MODULE INFO' with the bloom module name (e.g., 'MODULE INFO bloom' or 'MODULE INFO cms') to retrieve the module version.
    Affected if The version is 2.2.18 or earlier, 2.4.11 or earlier, 2.6.13 or earlier, or 2.8.1 or earlier.
  3. Verify CMS command availability
    Run 'COMMAND INFO CMS.INITBYDIM' to confirm the command is exposed by the module.
    Affected if The command returns information showing CMS.INITBYDIM is available.
  4. Confirm authentication is required
    Review Redis configuration (redis.conf) for 'requirepass' setting and verify that unauthenticated connections are rejected by attempting a connection without credentials.
    Affected if No password is set or authentication is disabled, meaning unauthenticated clients can execute CMS.INITBYDIM.

A system is affected if RedisBloom is loaded, the version is within the vulnerable ranges, and clients (even if authenticated) can execute the CMS.INITBYDIM command with large width/depth parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade RedisBloom to version 2.2.19, 2.4.12, 2.6.14, or 2.8.2 or later. If immediate upgrade is not possible, restrict Redis access to trusted clients only since valid authentication credentials are required for exploitation.

Recommended fix High confidence

RedisBloom 2.2.19, 2.4.12, 2.6.14, or 2.8.2 (choose the version appropriate for your Redis release)

  1. Identify the currently installed RedisBloom module version using `MODULE LIST` or checking your module load configuration
  2. Determine which RedisBloom release series you are using (2.2.x, 2.4.x, 2.6.x, or 2.8.x)
  3. Download the appropriate fixed version from the RedisBloom GitHub releases: 2.2.19, 2.4.12, 2.6.14, or 2.8.2
  4. Stop the Redis server gracefully using `redis-cli SHUTDOWN NOSAVE` or `systemctl stop redis`
  5. Replace the old RedisBloom module file with the new version
  6. Update the Redis configuration file (redis.conf) to load the new module version if explicitly specified
  7. Start the Redis server
  8. Verify the module is loaded with correct version using `MODULE LIST`

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-55656 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-55656 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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