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…
- Published
- Updated
- Reserved
- Assigned by
- mitre
Description
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| mitreCNA (assigner) | 3.0 | Low3.6 | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L |
| NVDNVD · Modified | 3.1 | Low3.6 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L |
- EPSS (exploitation in 30 days)
- 1.2% · top 32% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 3.6.
Weakness
Affected products
n/a
- affected n/a
References (7)
- https://drive.google.com/file/d/1oyR9DAZjZK_SCn3mor6NRAYLJS6ueXaY/view (opens in a new tab)x_refsource_MISCx_transferred
- USN-3817-2 (opens in a new tab)vendor-advisoryx_refsource_UBUNTUx_transferred
- GLSA-201811-02 (opens in a new tab)vendor-advisoryx_refsource_GENTOOx_transferred
- https://www.dropbox.com/sh/sj3ee7xv55j36k7/AADwP-YfOYikBMuy32e0uvPFa?dl=0 (opens in a new tab)x_refsource_MISCx_transferred
- USN-3817-1 (opens in a new tab)vendor-advisoryx_refsource_UBUNTUx_transferred
- https://bugs.python.org/issue31530 (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://www.oracle.com/security-alerts/cpujan2020.html (opens in a new tab)x_refsource_MISCx_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2018-1000030)Record last updated .