{"answers":{"affected":"1 open source package ship an affected version, including duckdb.","exploited":"There is no known exploitation of CVE-2024-22682 in the wild and no public exploit code.","fix":"Upgrade duckdb to 0.9.3.dev6 or later.","what":"CVE-2024-22682 is a vulnerability in duckdb, published on 30 Jan 2024."},"fix_prompt":"Check this codebase for CVE-2024-22682 and fix it if it is affected.\n\nWhat it is: CVE-2024-22682 is a vulnerability in duckdb, published on 30 Jan 2024. \nExploitation: There is no known exploitation of CVE-2024-22682 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- duckdb (PyPI): affected all versions; fixed in 0.9.3.dev6\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-22682/ (Markdown: https://insights.sbomify.com/CVE-2024-22682/index.md)","id":"CVE-2024-22682","markdown":"https://insights.sbomify.com/CVE-2024-22682/index.md","name":"CVE-2024-22682","record":{"aliases":["GHSA-fq57-m32w-cmv5","PYSEC-2024-25"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.","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":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2024-22682","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2024"},"n_packages":1,"n_references":0,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2024-22699"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.3.dev6"],"introduced":["0"],"last_affected":[],"package":"duckdb","purl":"pkg:pypi/duckdb","source":"PYSEC-2024-25"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-22667"},"products":[],"published":"2024-01-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2024-07-19","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2024-22682/"}