Skip to content
Heist/ feed
Back to feed
Low

CVE-2018-1000030 affecting package python-py 1.11.0-1

Type: advisorySources: OSV

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.

Products
python-py
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2018-1000030
Confirmed fixed CVEs
Not specified
Updated in this feed
1 Nov 2026, 17:27 UTC · Revision 1

Source evidence

CVE-2018-1000030 affecting package python-py 1.11.0-1

core-osv · Original source

Published 8 Feb 2018, 17:29 UTC

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.

osv:AZL-109623

python-py

Fixed versions: Not specified

Complete source record
{
  "id": "47072001e6438dbc5f2c39e47a8cda4f981b782e79d1d240c5e6455d72fedb4e",
  "url": "https://osv.dev/vulnerability/AZL-109623",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "CVE-2018-1000030 affecting package python-py 1.11.0-1",
    "summary": "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.",
    "evidence": "osv:AZL-109623",
    "products": [
      {
        "name": {
          "value": "python-py",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [],
        "affected_versions": []
      }
    ],
    "severity": "low",
    "structured": {
      "id": "AZL-109623",
      "aliases": [
        "AZL-109623"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "1.11.0-1"
                }
              ]
            }
          ],
          "package": {
            "name": "python-py",
            "purl": "pkg:rpm/azure-linux/python-py",
            "ecosystem": "Azure Linux:3"
          },
          "database_specific": {
            "source": "https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-109623.json"
          }
        }
      ],
      "modified": "2026-10-27T05:36:16Z",
      "provider": "osv",
      "upstream": [
        "CVE-2018-1000030"
      ],
      "references": [
        "https://nvd.nist.gov/vuln/detail/CVE-2018-1000030"
      ]
    },
    "related_cves": [
      {
        "value": "CVE-2018-1000030",
        "evidence": "/upstream"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 460499,
  "published_at": "2018-02-08T17:29:00+00:00"
}