{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2025-66564","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","state":"PUBLISHED","assignerShortName":"GitHub_M","dateReserved":"2025-12-04T16:05:22.975Z","datePublished":"2025-12-04T22:37:13.307Z","dateUpdated":"2025-12-05T14:55:53.273Z"},"containers":{"cna":{"title":"Sigstore Timestamp Authority allocates excessive memory during request parsing","problemTypes":[{"descriptions":[{"cweId":"CWE-405","lang":"en","description":"CWE-405: Asymmetric Resource Consumption (Amplification)","type":"CWE"}]}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":7.5,"baseSeverity":"HIGH","confidentialityImpact":"NONE","integrityImpact":"NONE","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}}],"references":[{"name":"https://github.com/sigstore/timestamp-authority/security/advisories/GHSA-4qg8-fj49-pxjh","tags":["x_refsource_CONFIRM"],"url":"https://github.com/sigstore/timestamp-authority/security/advisories/GHSA-4qg8-fj49-pxjh"},{"name":"https://github.com/sigstore/timestamp-authority/commit/0cae34e197d685a14904e0bad135b89d13b69421","tags":["x_refsource_MISC"],"url":"https://github.com/sigstore/timestamp-authority/commit/0cae34e197d685a14904e0bad135b89d13b69421"}],"affected":[{"vendor":"sigstore","product":"timestamp-authority","versions":[{"version":"< 2.0.3","status":"affected"}]}],"providerMetadata":{"orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M","dateUpdated":"2025-12-04T22:37:13.307Z"},"descriptions":[{"lang":"en","value":"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."}],"source":{"advisory":"GHSA-4qg8-fj49-pxjh","discovery":"UNKNOWN"}},"adp":[{"metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2025-12-05T14:55:44.658584Z","id":"CVE-2025-66564","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"title":"CISA ADP Vulnrichment","providerMetadata":{"orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP","dateUpdated":"2025-12-05T14:55:53.273Z"}}]}}