Python/numpy/0.9.6
Fundamental package for array computing in Python
https://pypi.org/project/numpy
BSD
7 Security Vulnerabilities
Numpy arbitrary file write via symlink attack
- https://nvd.nist.gov/vuln/detail/CVE-2014-1859
- https://github.com/numpy/numpy/pull/4262
- https://github.com/numpy/numpy/commit/0bb46c1448b0d3f5453d5182a17ea7ac5854ee15
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737778
- https://bugzilla.redhat.com/show_bug.cgi?id=1062009
- https://exchange.xforce.ibmcloud.com/vulnerabilities/91317
- https://github.com/numpy/numpy/blob/maintenance/1.8.x/doc/release/1.8.1-notes.rst
- http://lists.fedoraproject.org/pipermail/package-announce/2014-February/128358.html
- http://lists.fedoraproject.org/pipermail/package-announce/2014-February/128781.html
- http://www.openwall.com/lists/oss-security/2014/02/08/3
- https://github.com/advisories/GHSA-2fc2-6r4j-p65h
- https://github.com/pypa/advisory-database/tree/main/vulns/numpy/PYSEC-2018-34.yaml
- http://www.securityfocus.com/bid/65440
- https://web.archive.org/web/20200228165750/http://www.securityfocus.com/bid/65440
(1) core/tests/testmemmap.py, (2) core/tests/testmultiarray.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.
NumPy NULL Pointer Dereference
Null Pointer Dereference vulnerability exists in numpy.sort in NumPy < and 1.19 in the PyArray_DescrNew function due to missing return-value validation, which allows attackers to conduct DoS attacks by repetitively creating sort arrays.
Numpy Deserialization of Untrusted Data
- https://nvd.nist.gov/vuln/detail/CVE-2019-6446
- https://github.com/numpy/numpy/issues/12759
- https://bugzilla.suse.com/show_bug.cgi?id=1122208
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZZAYIQNUUYXGMKHSPEEXS4TRYFOUYE4/
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00091.html
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00092.html
- http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00015.html
- https://github.com/numpy/numpy/pull/12889
- https://web.archive.org/web/20210124234613/https://www.securityfocus.com/bid/106670/
- https://github.com/advisories/GHSA-9fq2-x9r6-wfmf
- https://access.redhat.com/errata/RHSA-2019:3335
- https://access.redhat.com/errata/RHSA-2019:3704
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/7ZZAYIQNUUYXGMKHSPEEXS4TRYFOUYE4
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZZAYIQNUUYXGMKHSPEEXS4TRYFOUYE4
- https://web.archive.org/web/20210124234613/https://www.securityfocus.com/bid/106670
- http://www.securityfocus.com/bid/106670
- https://github.com/pypa/advisory-database/tree/main/vulns/numpy/PYSEC-2019-108.yaml
** DISPUTED ** An issue was discovered in NumPy 1.16.0 and earlier. It uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object, as demonstrated by a numpy.load call. NOTE: third parties dispute this issue because it is a behavior that might have legitimate applications in (for example) loading serialized Python object arrays from trusted and authenticated sources.
Arbitrary file write in NumPy
- https://nvd.nist.gov/vuln/detail/CVE-2014-1858
- https://github.com/numpy/numpy/pull/4262
- https://github.com/numpy/numpy/commit/0bb46c1448b0d3f5453d5182a17ea7ac5854ee15
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737778
- https://bugzilla.redhat.com/show_bug.cgi?id=1062009
- https://exchange.xforce.ibmcloud.com/vulnerabilities/91318
- https://github.com/numpy/numpy/blob/maintenance/1.8.x/doc/release/1.8.1-notes.rst
- http://lists.fedoraproject.org/pipermail/package-announce/2014-February/128358.html
- http://lists.fedoraproject.org/pipermail/package-announce/2014-February/128781.html
- http://www.openwall.com/lists/oss-security/2014/02/08/3
- https://github.com/advisories/GHSA-cw6w-4rcx-xphc
- https://github.com/pypa/advisory-database/tree/main/vulns/numpy/PYSEC-2018-33.yaml
- http://www.securityfocus.com/bid/65441
init.py in f2py in NumPy before 1.8.1 allows local users to write to arbitrary files via a symlink attack on a temporary file.
Buffer Copy without Checking Size of Input in NumPy
Buffer overflow in the arrayfrompyobj function of fortranobject.c in NumPy < 1.19, which allows attackers to conduct a Denial of Service attacks by carefully constructing an array with negative values.
Incorrect Comparison in NumPy
- https://nvd.nist.gov/vuln/detail/CVE-2021-34141
- https://github.com/numpy/numpy/issues/18993
- https://github.com/advisories/GHSA-fpfv-jqm9-f5jm
- https://www.oracle.com/security-alerts/cpujul2022.html
- https://github.com/numpy/numpy/issues/18993#issuecomment-1010735102
- https://github.com/pypa/advisory-database/tree/main/vulns/numpy/PYSEC-2021-855.yaml
Incomplete string comparison in the numpy.core component in NumPy1.9.x, which allows attackers to fail the APIs via constructing specific string objects.
Numpy missing input validation
- https://nvd.nist.gov/vuln/detail/CVE-2017-12852
- https://github.com/numpy/numpy/issues/9560#issuecomment-322395292
- https://github.com/BT123/testcasesForMyRequest/tree/master/CVE-2017-12852
- https://github.com/numpy/numpy/releases/tag/v1.13.3
- https://github.com/advisories/GHSA-frgw-fgh6-9g52
- https://github.com/pypa/advisory-database/tree/main/vulns/numpy/PYSEC-2017-1.yaml
The numpy.pad function in Numpy 1.13.1 and older versions is missing input validation. An empty list or ndarray will stick into an infinite loop, which can allow attackers to cause a DoS attack.
177 Other Versions
| Version | License | Security | Released | |
|---|---|---|---|---|
| 1.8.1 | BSD | 5 | 2016-04-20 - 04:22 | almost 10 years |
| 1.8.0 | BSD | 7 | 2016-04-20 - 04:25 | almost 10 years |
| 1.7.2 | BSD | 7 | 2016-04-20 - 03:54 | almost 10 years |
| 1.7.1 | BSD | 7 | 2016-04-20 - 04:28 | almost 10 years |
| 1.7.0 | BSD | 7 | 2016-04-20 - 04:30 | almost 10 years |
| 1.6.2 | BSD | 7 | 2016-04-20 - 03:56 | almost 10 years |
| 1.6.1 | BSD | 7 | 2016-04-20 - 04:32 | almost 10 years |
| 1.6.0 | BSD | 7 | 2016-04-20 - 04:34 | almost 10 years |
| 1.5.1 | BSD | 7 | 2014-07-30 - 22:27 | over 11 years |
| 1.5.0 | BSD | 7 | 2010-09-15 - 14:44 | over 15 years |
| 1.4.1 | BSD | 7 | 2010-04-24 - 16:30 | almost 16 years |
| 1.4.0 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.3.0 | BSD | 7 | 2009-04-06 - 06:19 | about 17 years |
| 1.2.1 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.2.0 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.1.1 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.0.4 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.0.3 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.0 | BSD | 7 | 2006-12-02 - 02:07 | over 19 years |
| 0.9.8 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 0.9.6 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.0b4 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.0b5 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.0rc3 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.0b1 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.0rc1 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
| 1.0rc2 | BSD | 7 | 1970-01-01 - 00:00 | over 56 years |
