Bug 2419054 (CVE-2025-66564) - CVE-2025-66564 github.com/sigstore/timestamp-authority: Sigstore Timestamp Authority: Denial of Service via excessive OID or Content-Type header parsing
Summary: CVE-2025-66564 github.com/sigstore/timestamp-authority: Sigstore Timestamp Au...
Keywords:
Status: NEW
Alias: CVE-2025-66564
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2421864 2421865 2421866 2421867 2421868 2421869 2421870 2421871 2421872
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-12-04 23:02 UTC by OSIDB Bzimport
Modified: 2025-12-12 21:06 UTC (History)
24 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description OSIDB Bzimport 2025-12-04 23:02:08 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.