{"answers":{"affected":"3 open source packages ship an affected version, including numpy. It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-34141 in the wild and no public exploit code.","fix":"Upgrade numpy to a fixed version for your release line: 1.22 or 1.10.0.","what":"CVE-2021-34141 is a medium-severity vulnerability in Oracle Communications Cloud Native Core Policy, published on 17 Dec 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-34141 and fix it if it is affected.\n\nWhat it is: CVE-2021-34141 is a medium-severity vulnerability in Oracle Communications Cloud Native Core Policy, published on 17 Dec 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-34141 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- numpy (PyPI): affected all versions; fixed in 1.22\n- numpy (PyPI): affected all versions; fixed in 1.22\n- numpy (PyPI): affected from 1.9.0; fixed in 1.10.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-2021-34141/ (Markdown: https://insights.sbomify.com/CVE-2021-34141/index.md)","id":"CVE-2021-34141","markdown":"https://insights.sbomify.com/CVE-2021-34141/index.md","name":"CVE-2021-34141","record":{"aliases":["CLSA-2025-1760400833","CLSA-2026-1781139192","DEBIAN-CVE-2021-34141","ECHO-4195-024c-0bcd","GHSA-fpfv-jqm9-f5jm","MINI-wq6v-xg86-wg83","PYSEC-2021-855","UBUNTU-CVE-2021-34141"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Python numerical library","requires_auth":"none","summary":"An incomplete string comparison in NumPy allows attackers to trigger slightly incorrect copying, though the vendor deems the behavior harmless.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"numpy","vendor":"numpy"},{"product":"communications_cloud_native_core_policy","vendor":"oracle"}],"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-697","name":"Incorrect Comparison"}],"description":"An incomplete string comparison in the numpy.core component in NumPy before 1.22.0 allows attackers to trigger slightly incorrect copying by constructing specific string objects. NOTE: the vendor states that this reported code behavior is \"completely harmless.\"","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":"Incorrect Comparison in NumPy","id":"CVE-2021-34141","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"oracle:communications_cloud_native_core_policy","products":["oracle:communications_cloud_native_core_policy"],"type":"other","year":"2021"},"n_packages":3,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2021-34143"},"packages":[{"ecosystem":"PyPI","fixed":["1.22"],"introduced":["0"],"last_affected":[],"package":"numpy","purl":null,"source":"GHSA-fpfv-jqm9-f5jm"},{"ecosystem":"PyPI","fixed":["1.22"],"introduced":["0"],"last_affected":[],"package":"numpy","purl":"pkg:pypi/numpy","source":"GHSA-fpfv-jqm9-f5jm"},{"ecosystem":"PyPI","fixed":["1.10.0"],"introduced":["1.9.0"],"last_affected":[],"package":"numpy","purl":"pkg:pypi/numpy","source":"PYSEC-2021-855"}],"prev":{"headline":"Path traversal in n/a","id":"CVE-2021-34129"},"products":["n/a"],"published":"2021-12-17","related":[{"cvss_score":7.5,"headline":"Numpy missing input validation","id":"CVE-2017-12852","kev_date_added":null,"published":"2017-08-15"},{"cvss_score":5.5,"headline":"Buffer Copy without Checking Size of Input in NumPy","id":"CVE-2021-41496","kev_date_added":null,"published":"2021-12-17"},{"cvss_score":5.5,"headline":"Arbitrary file write in NumPy","id":"CVE-2014-1858","kev_date_added":null,"published":"2018-01-08"},{"cvss_score":5.3,"headline":"NumPy Buffer Overflow (Disputed)","id":"CVE-2021-33430","kev_date_added":null,"published":"2021-12-17"},{"cvss_score":5.3,"headline":"NumPy NULL Pointer Dereference","id":"CVE-2021-41495","kev_date_added":null,"published":"2021-12-17"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["n/a"]},"summary":"An incomplete string comparison in NumPy allows attackers to trigger slightly incorrect copying, though the vendor deems the behavior harmless.","url":"https://insights.sbomify.com/CVE-2021-34141/"}