LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19274: typed_ast 1.3.0 and 1.3.1 has a handle_keywordonly_args out-of-bounds read.

typed_ast 1.3.0 and 1.3.1 has a handle_keywordonly_args out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not execute) Python code. (This issue also affected certain Python 3.8.0-alpha prereleases.)

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

typed_ast 1.3.0 and 1.3.1 could crash a Python process when parsing specially formed Python source. This matters mainly for services that accept and parse untrusted Python code, even if they do not execute it.

Executive priority

Treat as a targeted availability risk, not a broad emergency. Prioritize remediation where customer-facing or shared services parse untrusted Python code, because crashes could disrupt service availability.

Technical view

The issue is an out-of-bounds read in handle_keywordonly_args in typed_ast 1.3.0 and 1.3.1. The CVE states an attacker who can cause parsing of Python source may crash the interpreter process. Certain Python 3.8.0-alpha prereleases were also affected.

Likely exposure

Exposure is most likely in developer tools, code analysis services, education platforms, CI systems, or web applications that parse user-submitted Python source using affected typed_ast versions.

Exploitation context

The source bundle does not show KEV listing or active exploitation. The described impact is denial of service through interpreter crash, not code execution. Exploitation requires a path to make the target parse attacker-controlled Python source.

Researcher notes

Evidence is sufficient for affected typed_ast versions, affected behavior, and crash impact. The bundle lacks CVSS, CWE, proof of active exploitation, and a named fixed release, so remediation should be tied to upstream or distribution guidance.

Mitigation direction

  • Inventory typed_ast usage and identify versions 1.3.0 or 1.3.1.
  • Apply vendor or package updates that include the referenced typed_ast fixes.
  • Check whether any environment uses affected Python 3.8.0-alpha prereleases.
  • Reduce or isolate parsing of untrusted Python source where practical.
  • Review Fedora or distribution advisories for packaged remediation status.

Validation and detection

  • Confirm package manifests and runtime environments do not use typed_ast 1.3.0 or 1.3.1.
  • Identify public or internal endpoints that parse submitted Python source.
  • Verify updated packages include the referenced upstream fix commits.
  • Test parser-facing services for graceful failure and process supervision.
  • Document remaining exposure where parsing untrusted Python cannot be removed.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-19274 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.