GHSA-4qg8-fj49-pxjh
Suggest an improvement- Source
- https://github.com/advisories/GHSA-4qg8-fj49-pxjh
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/12/GHSA-4qg8-fj49-pxjh/GHSA-4qg8-fj49-pxjh.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/GHSA-4qg8-fj49-pxjh
- Aliases
- Downstream
- Published
- 2025-12-05T18:19:00Z
- Modified
- 2025-12-05T18:31:08.670762Z
- Severity
-
- 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- 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-Typeheader (which is also untrusted data) on anapplicationstring.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-Typeheader, a call toapi.ParseJSONRequestorapi.getContentTypeincurs 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.
- Database specific
{ "github_reviewed": true, "nvd_published_at": "2025-12-04T23:15:47Z", "severity": "HIGH", "cwe_ids": [ "CWE-405" ], "github_reviewed_at": "2025-12-05T18:19:00Z" }- References
Affected packages
Go / github.com/sigstore/timestamp-authority
Package
- Name
- github.com/sigstore/timestamp-authority
- View open source insights on deps.dev
- Purl
- pkg:golang/github.com/sigstore/timestamp-authority