Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Temporal Technologies, Inc. temporalio/sqlparser
Default version status: unaffected
0.0.0-20180604150908-b055e9c9b4fa to < 0.0.0-20260721183040-74181ffcbaafaffected
Temporal Technologies, Inc. Temporal Server
Default version status: unaffected
1.29.0 to ≤ 1.29.7affected1.30.0 to < 1.30.7affected1.31.0 to < 1.31.3affected
References
- https://github.com/temporalio/sqlparser/pull/5 ↗
- https://github.com/temporalio/sqlparser/commit/74181ffcbaaf0c52faa925f4cf27ed6c0c2be86f ↗
- https://github.com/temporalio/sqlparser/tree/v0.1.0 ↗
- https://github.com/temporalio/temporal/pull/11190 ↗
- https://github.com/temporalio/temporal/pull/11090 ↗
- https://github.com/temporalio/temporal/releases/tag/v1.30.7 ↗
- https://github.com/temporalio/temporal/releases/tag/v1.31.3 ↗