| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Python up to 2.7.13. It has been classified as critical. Impacted is an unknown function. This manipulation causes memory corruption. This vulnerability is handled as CVE-2018-1000030. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical was found in Python up to 2.7.13 (Programming Language Software). Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Python 2.7.14 is vulnerable to a Heap-Buffer-Overflow as well as a Heap-Use-After-Free. Python versions prior to 2.7.14 may also be vulnerable and it appears that Python 2.7.17 and prior may also be vulnerable however this has not been confirmed. The vulnerability lies when multiply threads are handling large amounts of data. In both cases there is essentially a race condition that occurs. For the Heap-Buffer-Overflow, Thread 2 is creating the size for a buffer, but Thread1 is already writing to the buffer without knowing how much to write. So when a large amount of data is being processed, it is very easy to cause memory corruption using a Heap-Buffer-Overflow. As for the Use-After-Free, Thread3->Malloc->Thread1->Free's->Thread2-Re-uses-Free'd Memory. The PSRT has stated that this is not a security vulnerability due to the fact that the attacker must be able to run code, however in some situations, such as function as a service, this vulnerability can potentially be used by an attacker to violate a trust boundary, as such the DWF feels this issue deserves a CVE.
The bug was discovered 09/20/2017. The weakness was released 02/08/2018 (Website). The advisory is shared at bugs.python.org. This vulnerability is known as CVE-2018-1000030 since 02/08/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 141 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 110037 (SUSE SLED12 / SLES12 Security Update : python (SUSE-SU-2018:1372-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 197302 (Ubuntu Security Notification for Python2.7, Python3.4, Python3.5 Vulnerabilities (USN-3817-1)).
Upgrading to version 2.7.14 eliminates this vulnerability. A possible mitigation has been published 4 months after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (110037) and SecurityFocus (BID 105396†). Entries connected to this vulnerability are available at VDB-109585, VDB-119652, VDB-119653 and VDB-124167. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.6
NVD Vector: 🔍
CNA Base Score: 3.6
CNA Vector (MITRE): 🔍
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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 |
Nessus ID: 110037
Nessus Name: SUSE SLED12 / SLES12 Security Update : python (SUSE-SU-2018:1372-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 56008
OpenVAS Name: SuSE Update for python openSUSE-SU-2018:1415-1 (python)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Python 2.7.14
Timeline
09/20/2017 🔍02/08/2018 🔍
02/08/2018 🔍
02/08/2018 🔍
02/09/2018 🔍
05/22/2018 🔍
05/23/2018 🔍
09/22/2018 🔍
02/06/2023 🔍
Sources
Advisory: USN-3817-1Researcher: The Python Security Response Team.
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-1000030 (🔍)
GCVE (CVE): GCVE-0-2018-1000030
GCVE (VulDB): GCVE-100-113041
OVAL: 🔍
SecurityFocus: 105396 - Python CVE-2018-14647 Remote Denial of Service Vulnerability
See also: 🔍
Entry
Created: 02/09/2018 08:49Updated: 02/06/2023 08:47
Changes: 02/09/2018 08:49 (60), 01/03/2020 10:04 (12), 02/03/2021 07:41 (13), 02/03/2021 07:44 (1), 02/06/2023 08:42 (2), 02/06/2023 08:47 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.