sigstore
Affected
- introduced
2.0.0, fixed3.6.0(ecosystem)
Fixed versions
3.6.0
Fix
- Fixed version
3.6.0pip install --upgrade sigstore==3.6.0
Advisory
Also known as: CVE-2024-55655, GHSA-hhfg-fwrw-87w7
sigstore has insufficient validation of integration timestamp during verification
Summary
Versions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified *if* a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present.
This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise.
Details
Sigstore uses signed time to support verification of signatures made against short-lived signing keys.
Impact
The impact and severity of this weakness is *low*, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify).
Separately, an attacker could upload a *new* entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable.
Not rated by the source.
2.0.0, fixed 3.6.0 (ecosystem)3.6.0
3.6.0pip install --upgrade sigstore==3.6.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0