HighGHSA-2fc2-6r4j-p65hCVE-2014-1859PYSEC-2018-34

Numpy arbitrary file write via symlink attack

Published 14 May 2022 · Updated 1 Oct 2024

Is your project on an affected numpy?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

numpyPyPI
Affected
<1.8.1
Fixed in
1.8.1
Update to the fixed version for your release line, for example:pip install 'numpy>=1.8.1'

Details

(1) core/tests/test_memmap.py, (2) core/tests/test_multiarray.py, (3) f2py/f2py2e.py, and (4) lib/tests/test_io.py in NumPy before 1.8.1 allow local users to write to arbitrary files via a symlink attack on a temporary file.

Is GHSA-2fc2-6r4j-p65h 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-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
  • MediumCVE-2021-33430NumPy Buffer Overflow (Disputed) · 7 Jan 2022
All 8 advisories for numpy

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.