CVE-2025-66564
Sigstore Timestamp Authority allocates excessive memory during request parsing
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2025-66564 divulgada · CVSS 7.5 (CNA) | |
| Remediación | Parche v2.0.3 | github.com/sigstore/timestamp-authority/v2 · 0 d desde divulgación | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
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.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/sigstore/timestamp-authority |
Sin parche | — | — | v1.2.9 afectada |
gogithub.com/sigstore/timestamp-authority/v2 |
Corregida | v2.0.3 | 0 d | v2.2.0 no afectada |
2.0.3v2.0.3Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/sigstore/timestamp-authority/security/advisories/GHSA-4qg8-fj49-pxjhhttps://github.com/sigstore/timestamp-authority/commit/0cae34e197d685a14904e0bad135b89d13b69421Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
