github.com/sigstore/timestamp-authority
Affected
- introduced
0, fixed2.0.3(semver)
Fixed versions
2.0.3
Fix
- Fixed version
2.0.3go get github.com/sigstore/[email protected]
Advisory
Also known as: CVE-2025-66564, GO-2025-4192
Sigstore Timestamp Authority allocates excessive memory during request parsing
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.
High Basis: The source's own band: HIGH
0, fixed 2.0.3 (semver)2.0.3
2.0.3go get github.com/sigstore/[email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0