NumPy Buffer Overflow (Disputed)
Published 7 Jan 2022 · Updated 26 Sept 2024
Is your project on an affected numpy?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=1.9.0 <1.21
- Fixed in
- 1.21
pip install 'numpy>=1.21'Details
A Buffer Overflow vulnerability exists in NumPy 1.9.x in the PyArray_NewFromDescr_int function of ctors.c when specifying arrays of large dimensions (over 32) from Python code, which could let a malicious user cause a Denial of Service.
NOTE: The vendor does not agree this is a vulnerability; In (very limited) circumstances a user may be able provoke the buffer overflow, the user is most likely already privileged to at least provoke denial of service by exhausting memory. Triggering this further requires the use of uncommon API (complicated structured dtypes), which is very unlikely to be available to an unprivileged user.
Is GHSA-6p56-wp2h-9hxr in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected numpy, and gives you the command that fixes it.
More advisories for numpy
- CriticalCVE-2019-6446Numpy Deserialization of Untrusted Data · 24 May 2022
- HighCVE-2014-1858Arbitrary file write in NumPy · 14 May 2022
- HighCVE-2014-1859Numpy arbitrary file write via symlink attack · 14 May 2022
- HighCVE-2017-12852Numpy missing input validation · 13 May 2022
- HighCVE-2021-41495NumPy NULL Pointer Dereference · 8 Feb 2022
- MediumCVE-2021-41496Buffer Copy without Checking Size of Input in NumPy · 8 Feb 2022
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.