temporalio/sqlparser can panic when Parse, ParseStrictDDL, or ParseNext processes a MySQL version comment whose contents are empty or consist only of one to five decimal digits. ExtractMysqlComment does not check the -1 result returned by strings.IndexFunc before using it as a slice boundary. The resulting Go runtime panic propagates unless the caller recovers it on the parsing goroutine, so applications that parse attacker-controlled SQL can terminate. Temporal Server exposes the affected parser through ListWorkers. When that API is enabled, an authenticated caller with namespace read permission can submit a malformed query that terminates the receiving Matching process. Repeated requests can sustain a denial of service. The issue affects availability only; no confidentiality or integrity impact was identified.
Summary
AItemporalio/sqlparser can panic when it parses a MySQL version comment that is empty or contains only one to five decimal digits. Applications parsing attacker-controlled SQL can terminate unless they recover the panic on the parsing goroutine. In Temporal Server, an authenticated caller with namespace read permission can submit such a query through ListWorkers, when that API is enabled, to terminate the receiving Matching process; repeated requests can sustain a denial of service.
Who should check
Engineers running temporalio/sqlparser or Temporal Server should check their deployments; affected versions were not specified.
What to do
- 1Consult the vendor advisory for affected and fixed versions.
- 2Update affected deployments according to the advisory.