{"answers":{"affected":"3 open source packages ship an affected version, including numpy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41496 in the wild and no public exploit code.","fix":"Upgrade numpy to a fixed version for your release line: 1.19 or 1.19.0.","what":"CVE-2021-41496 is a medium-severity denial of service vulnerability in n/a, published on 17 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41496 and fix it if it is affected.\n\nWhat it is: CVE-2021-41496 is a medium-severity denial of service vulnerability in n/a, published on 17 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-41496 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- numpy (PyPI): affected all versions; fixed in 1.19\n- numpy (PyPI): affected all versions; fixed in 1.19\n- numpy (PyPI): affected all versions; fixed in 1.19.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-41496/ (Markdown: https://insights.sbomify.com/CVE-2021-41496/index.md)","id":"CVE-2021-41496","markdown":"https://insights.sbomify.com/CVE-2021-41496/index.md","name":"CVE-2021-41496","record":{"aliases":["AZL-7056","CLSA-2025-1766621635","CLSA-2026-1791368060","DEBIAN-CVE-2021-41496","ECHO-70fc-d0bb-2f7d","GHSA-f7c7-j99h-c22f","MINI-35fr-chh2-cc57","OESA-2022-1485","PYSEC-2021-857","UBUNTU-CVE-2021-41496"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NumPy library","requires_auth":"low_privilege","summary":"A buffer overflow in NumPy allows attackers to cause a denial of service by constructing arrays with negative values, though vendor disputes severity.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"numpy","vendor":"numpy"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Buffer overflow in the array_from_pyobj function of fortranobject.c in NumPy \u003c 1.19, which allows attackers to conduct a Denial of Service attacks by carefully constructing an array with negative values. NOTE: The vendor does not agree this is a vulnerability; the negative dimensions can only be created by an already privileged user (or internally)","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":"Buffer Copy without Checking Size of Input in NumPy","id":"CVE-2021-41496","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2021"},"n_packages":3,"n_references":2,"next":{"headline":"bounter Null pointer reference","id":"CVE-2021-41497"},"packages":[{"ecosystem":"PyPI","fixed":["1.19"],"introduced":["0"],"last_affected":[],"package":"numpy","purl":null,"source":"GHSA-f7c7-j99h-c22f"},{"ecosystem":"PyPI","fixed":["1.19"],"introduced":["0"],"last_affected":[],"package":"numpy","purl":"pkg:pypi/numpy","source":"GHSA-f7c7-j99h-c22f"},{"ecosystem":"PyPI","fixed":["1.19.0"],"introduced":["0"],"last_affected":[],"package":"numpy","purl":"pkg:pypi/numpy","source":"PYSEC-2021-857"}],"prev":{"headline":"NumPy NULL Pointer Dereference","id":"CVE-2021-41495"},"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":"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":"Incorrect Comparison in NumPy","id":"CVE-2021-34141","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"A buffer overflow in NumPy allows attackers to cause a denial of service by constructing arrays with negative values, though vendor disputes severity.","url":"https://insights.sbomify.com/CVE-2021-41496/"}