Numpy up to 1.16.0 Pickle Python Serialized Object deserialization ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Numpy up to 1.16.0. The impacted element is an unknown function of the component Pickle Python Module. Executing a manipulation as part of Serialized Object can lead to deserialization. This vulnerability is handled as CVE-2019-6446. The attack can be executed remotely. There is not any exploit available. The existence of this vulnerability is still disputed at present.
Details
A vulnerability was found in Numpy up to 1.16.0. It has been declared as critical. This vulnerability affects some unknown functionality of the component Pickle Python Module. The manipulation as part of a Serialized Object leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The bug was discovered 01/16/2019. The weakness was released 01/16/2019 (Website). The advisory is shared for download at securityfocus.com. This vulnerability was named CVE-2019-6446 since 01/15/2019. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.
The real existence of this vulnerability is still doubted at the moment. The commercial vulnerability scanner Qualys is able to test this issue with plugin 172117 (OpenSUSE Security Update for python-numpy (openSUSE-SU-2019:0245-1)).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 106670†). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.0VulDB Meta Temp Score: 9.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 9.8
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/15/2019 🔍01/16/2019 🔍
01/16/2019 🔍
01/16/2019 🔍
01/16/2019 🔍
01/16/2019 🔍
08/04/2024 🔍
Sources
Advisory: RHSA-2019:3335⛔Status: Not defined
Disputed: 🔍
CVE: CVE-2019-6446 (🔍)
GCVE (CVE): GCVE-0-2019-6446
GCVE (VulDB): GCVE-100-129796
SecurityFocus: 106670 - NumPy CVE-2019-6446 Pickle Arbitrary Code Execution Vulnerability
Entry
Created: 01/16/2019 13:35Updated: 08/04/2024 23:33
Changes: 01/16/2019 13:35 (59), 05/02/2020 06:48 (3), 07/01/2023 10:06 (3), 08/04/2024 23:33 (28)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.