Advisory

GHSA-4qg8-fj49-pxjh

Also known as: CVE-2025-66564, GO-2025-4192

Summary

Sigstore Timestamp Authority allocates excessive memory during request parsing

Details

Impact

Excessive memory allocation

Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string.

As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). Relevant weakness: CWE-405: Asymmetric Resource Consumption (Amplification)

Patches

Upgrade to v2.0.3.

Workarounds

There are no workarounds with the service itself. If the service is behind a load balancer, configure the load balancer to reject excessively large requests.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-12-05 18:19 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/sigstore/timestamp-authority

Go · All systems

Affected

  • introduced 0, fixed 2.0.3 (semver)

Fixed versions

2.0.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences