Vulnerability Details : CVE-2018-1000030
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.
Vulnerability category: OverflowMemory Corruption
Products affected by CVE-2018-1000030
- cpe:2.3:o:canonical:ubuntu_linux:14.04:*:*:*:lts:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:12.04:*:*:*:esm:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
- cpe:2.3:a:python:python:*:*:*:*:*:*:*:*
Threat overview for CVE-2018-1000030
Top countries where our scanners detected CVE-2018-1000030
Top open port discovered on systems with this issue
80
IPs affected by CVE-2018-1000030 34,762
Threat actors abusing to this issue?
Yes
Find out if you* are
affected by CVE-2018-1000030!
*Directly or indirectly through your vendors, service providers and 3rd parties.
Powered by
attack surface intelligence
from SecurityScorecard.
Exploit prediction scoring system (EPSS) score for CVE-2018-1000030
0.08%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 31 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2018-1000030
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
3.3
|
LOW | AV:L/AC:M/Au:N/C:P/I:N/A:P |
3.4
|
4.9
|
NIST | |
3.6
|
LOW | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L |
1.0
|
2.5
|
MITRE | |
3.6
|
LOW | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L |
1.0
|
2.5
|
NIST |
CWE ids for CVE-2018-1000030
-
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.Assigned by: nvd@nist.gov (Primary)
-
The product writes data past the end, or before the beginning, of the intended buffer.Assigned by: nvd@nist.gov (Primary)
References for CVE-2018-1000030
-
https://www.oracle.com/security-alerts/cpujan2020.html
Oracle Critical Patch Update Advisory - January 2020Third Party Advisory
-
https://usn.ubuntu.com/3817-2/
USN-3817-2: Python vulnerabilities | Ubuntu security noticesThird Party Advisory
-
https://bugs.python.org/issue31530
Issue 31530: CVE-2018-1000030: Python 2.7 readahead feature of file objects is not thread safe - Python trackerIssue Tracking;Patch;Vendor Advisory
-
https://security.gentoo.org/glsa/201811-02
Python: Buffer overflow (GLSA 201811-02) — Gentoo securityThird Party Advisory
-
https://www.dropbox.com/sh/sj3ee7xv55j36k7/AADwP-YfOYikBMuy32e0uvPFa?dl=0
Dropbox - Python Bug - Simplify your lifePermissions Required
-
https://drive.google.com/file/d/1oyR9DAZjZK_SCn3mor6NRAYLJS6ueXaY/view
Python Use-After-Free Description.pdf - Google DriveThird Party Advisory
-
https://usn.ubuntu.com/3817-1/
USN-3817-1: Python vulnerabilities | Ubuntu security noticesThird Party Advisory
Jump to