{"answers":{"affected":"3 open source packages ship an affected version, including scipy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-29824 in the wild and no public exploit code.","fix":"Upgrade scipy to 1.8.0 or later.","what":"CVE-2023-29824 is a critical use after free vulnerability in n/a, published on 6 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-29824 and fix it if it is affected.\n\nWhat it is: CVE-2023-29824 is a critical use after free vulnerability in n/a, published on 6 Jul 2023. 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-2023-29824 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- scipy (PyPI): affected all versions; fixed in 1.8.0\n- scipy (PyPI): affected all versions; fixed in 1.8.0\n- scipy (PyPI): affected all versions; fixed in 1.8.0\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-29824/ (Markdown: https://insights.sbomify.com/CVE-2023-29824/index.md)","id":"CVE-2023-29824","markdown":"https://insights.sbomify.com/CVE-2023-29824/index.md","name":"CVE-2023-29824","record":{"aliases":["DEBIAN-CVE-2023-29824","GHSA-jrfm-2h82-xg28","PYSEC-2023-114"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Python scientific library","requires_auth":"none","summary":"A use-after-free flaw in SciPy's Py_FindObjects function was reported, though the vendor states it is not a security issue.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"scipy","vendor":"scipy"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"A use-after-free issue was discovered in Py_FindObjects() function in SciPy versions prior to 1.8.0. NOTE: the vendor and discoverer indicate that this is not a security issue.","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":"Withdrawn: Use after free in SciPy","id":"CVE-2023-29824","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"use_after_free","year":"2023"},"n_packages":3,"n_references":4,"next":{"headline":"Code injection in n/a","id":"CVE-2023-29827"},"packages":[{"ecosystem":"PyPI","fixed":["1.8.0"],"introduced":["0"],"last_affected":[],"package":"scipy","purl":null,"source":"GHSA-jrfm-2h82-xg28"},{"ecosystem":"PyPI","fixed":["1.8.0"],"introduced":["0"],"last_affected":[],"package":"scipy","purl":"pkg:pypi/scipy","source":"GHSA-jrfm-2h82-xg28"},{"ecosystem":"PyPI","fixed":["1.8.0"],"introduced":["0"],"last_affected":[],"package":"scipy","purl":"pkg:pypi/scipy","source":"PYSEC-2023-114"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2023-29820"},"products":["n/a"],"published":"2023-07-06","related":[{"cvss_score":5.5,"headline":"Withdrawn: scipy memory leak vulnerability","id":"CVE-2023-25399","kev_date_added":null,"published":"2023-07-05"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"A use-after-free flaw in SciPy's Py_FindObjects function was reported, though the vendor states it is not a security issue.","url":"https://insights.sbomify.com/CVE-2023-29824/"}