Sigstore Timestamp Authority allocates excessive memory during request parsing
sigstore timestamp-authority
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/sigstore/timestamp-authority Go |
|
|
| github.com/sigstore/timestamp-authority/v2 Go |
|
|
sigstore timestamp-authority
| Product | Affected | Fixed in |
|---|---|---|
| github.com/sigstore/timestamp-authority Go |
|
|
| github.com/sigstore/timestamp-authority/v2 Go |
|
|
Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, 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). This vulnerability is fixed in 2.0.3.
From the CVE record · GitHub_M
Sigstore Timestamp Authority allocates memory proportional to the length of an untrusted OID or Content-Type header when parsing requests. An attacker can send a malicious request with an excessively long, period-filled OID or a malformed Content-Type header to trigger these allocations; no user interaction is required.
Engineers running sigstore timestamp-authority or using the Go packages github.com/sigstore/timestamp-authority and github.com/sigstore/timestamp-authority/v2 should check versions before 2.0.3.