{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-55656 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-55656 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-55656 is a high-severity vulnerability in RedisBloom, published on 8 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-55656 and fix it if it is affected.\n\nWhat it is: CVE-2024-55656 is a high-severity vulnerability in RedisBloom, published on 8 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-55656 in the wild and no public exploit code.\n\nAffected product: RedisBloom. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-55656/ (Markdown: https://insights.sbomify.com/CVE-2024-55656/index.md)","id":"CVE-2024-55656","markdown":"https://insights.sbomify.com/CVE-2024-55656/index.md","name":"CVE-2024-55656","record":{"aliases":["GHSA-x5rx-rmq3-ff3h"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"RedisBloom module","requires_auth":"low_privilege","summary":"An integer overflow in RedisBloom allows authenticated attackers to trigger out-of-bounds writes, potentially leading to remote code execution or information disclosure.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-05-20","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-05-20T14:01:46Z","kind":"github_poc","ref":"https://github.com/rick2600/redis-stack-CVE-2024-55656","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":false,"headline":"RedisBloom Integer Overflow Remote Code Execution Vulnerability","id":"CVE-2024-55656","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"SiYuan has an arbitrary file read via /api/template/render","id":"CVE-2024-55657"},"packages":[],"prev":{"headline":"sigstore-python has insufficient validation of integration timestamp during verification","id":"CVE-2024-55655"},"products":["RedisBloom"],"published":"2025-01-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-08","vendors":["RedisBloom"]},"summary":"An integer overflow in RedisBloom allows authenticated attackers to trigger out-of-bounds writes, potentially leading to remote code execution or information disclosure.","url":"https://insights.sbomify.com/CVE-2024-55656/"}