{"answers":{"affected":"5 open source packages ship an affected version, including redis. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-28859 in the wild and no public exploit code.","fix":"Upgrade redis to a fixed version for your release line: 4.4.4 or 4.5.4.","what":"CVE-2023-28859 is a medium-severity vulnerability in n/a, published on 26 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-28859 and fix it if it is affected.\n\nWhat it is: CVE-2023-28859 is a medium-severity vulnerability in n/a, published on 26 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-28859 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- redis (PyPI): affected from 4.2.0; fixed in 4.4.4, 4.5.4\n- redis (PyPI): affected from 4.2.0; fixed in 4.4.4\n- redis (PyPI): affected from 4.2.0; fixed in 4.4.4\n- redis (PyPI): affected from 4.5.0; fixed in 4.5.4\n- redis (PyPI): affected from 4.5.0; fixed in 4.5.4\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-2023-28859/ (Markdown: https://insights.sbomify.com/CVE-2023-28859/index.md)","id":"CVE-2023-28859","markdown":"https://insights.sbomify.com/CVE-2023-28859/index.md","name":"CVE-2023-28859","record":{"aliases":["GHSA-8fww-64cx-x8p5","PYSEC-2023-46","UBUNTU-CVE-2023-28859"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python Redis client","requires_auth":"low_privilege","summary":"An attacker can read response data from unrelated requests due to connection leakage in the async Redis client.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"redis-py","vendor":"redis"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-459","name":"Incomplete Cleanup"}],"description":"redis-py before 4.4.4 and 4.5.x before 4.5.4 leaves a connection open after canceling an async Redis command at an inopportune time, and can send response data to the client of an unrelated request. (This could, for example, happen for a non-pipeline operation.) NOTE: the solutions for CVE-2023-28859 address data leakage across AsyncIO connections in general.","ecosystems":["PyPI"],"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":"redis-py Race Condition due to incomplete fix","id":"CVE-2023-28859","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":5,"n_references":5,"next":{"headline":"Auth bypass in n/a","id":"CVE-2023-28862"},"packages":[{"ecosystem":"PyPI","fixed":["4.4.4","4.5.4"],"introduced":["4.2.0","4.5.0"],"last_affected":[],"package":"redis","purl":"pkg:pypi/redis","source":"PYSEC-2023-46"},{"ecosystem":"PyPI","fixed":["4.4.4"],"introduced":["4.2.0"],"last_affected":[],"package":"redis","purl":null,"source":"GHSA-8fww-64cx-x8p5"},{"ecosystem":"PyPI","fixed":["4.4.4"],"introduced":["4.2.0"],"last_affected":[],"package":"redis","purl":"pkg:pypi/redis","source":"GHSA-8fww-64cx-x8p5"},{"ecosystem":"PyPI","fixed":["4.5.4"],"introduced":["4.5.0"],"last_affected":[],"package":"redis","purl":null,"source":"GHSA-8fww-64cx-x8p5"},{"ecosystem":"PyPI","fixed":["4.5.4"],"introduced":["4.5.0"],"last_affected":[],"package":"redis","purl":"pkg:pypi/redis","source":"GHSA-8fww-64cx-x8p5"}],"prev":{"headline":"redis-py Race Condition vulnerability","id":"CVE-2023-28858"},"products":["n/a"],"published":"2023-03-26","related":[{"cvss_score":3.7,"headline":"redis-py Race Condition vulnerability","id":"CVE-2023-28858","kev_date_added":null,"published":"2023-03-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-20","vendors":["n/a"]},"summary":"An attacker can read response data from unrelated requests due to connection leakage in the async Redis client.","url":"https://insights.sbomify.com/CVE-2023-28859/"}