{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-3470 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-3470 is a medium-severity memory corruption vulnerability in redis, published on 31 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-3470 and fix it if it is affected.\n\nWhat it is: CVE-2021-3470 is a medium-severity memory corruption vulnerability in redis, published on 31 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-3470 in the wild and no public exploit code.\n\nAffected product: redis. 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-2021-3470/ (Markdown: https://insights.sbomify.com/CVE-2021-3470/index.md)","id":"CVE-2021-3470","markdown":"https://insights.sbomify.com/CVE-2021-3470/index.md","name":"CVE-2021-3470","record":{"aliases":["ALPINE-CVE-2021-3470","AZL-6852","CLEANSTART-2026-BW73910","DEBIAN-CVE-2021-3470","GHSA-mqmr-8cxh-pqf6","OESA-2021-1172","UBUNTU-CVE-2021-3470"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Redis database","requires_auth":"none","summary":"Heap overflow in Redis when using non-standard allocators allows out-of-bounds writes, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"redis","vendor":"redislabs"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A heap overflow issue was found in Redis in versions before 5.0.10, before 6.0.9 and before 6.2.0 when using a heap allocator other than jemalloc or glibc's malloc, leading to potential out of bound write or process crash. Effectively this flaw does not affect the vast majority of users, who use jemalloc or glibc malloc.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in redis","id":"CVE-2021-3470","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2021-3471"},"packages":[],"prev":{"headline":"Missing authorization in Foreman","id":"CVE-2021-3469"},"products":["redis"],"published":"2021-03-31","related":[{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2017-15047","kev_date_added":null,"published":"2017-10-06"},{"cvss_score":8.4,"headline":"Memory corruption in n/a","id":"CVE-2018-12326","kev_date_added":null,"published":"2018-06-17"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2020-21468","kev_date_added":null,"published":"2021-09-20"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2018-12453","kev_date_added":null,"published":"2018-06-16"},{"cvss_score":7.4,"headline":"Other in n/a","id":"CVE-2016-10517","kev_date_added":null,"published":"2017-10-24"},{"cvss_score":6.6,"headline":"Memory corruption in Redis","id":"CVE-2016-8339","kev_date_added":null,"published":"2016-10-28"},{"cvss_score":5.5,"headline":"Other in Redis","id":"CVE-2013-0178","kev_date_added":null,"published":"2019-11-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Heap overflow in Redis when using non-standard allocators allows out-of-bounds writes, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2021-3470/"}