CVE-2024-55655

描述

### 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.

如何修補 CVE-2024-55655

要修補 CVE-2024-55655,請將受影響套件升級到下列已修補版本。

• —升級至 3.6.0 或更新版本

CVE-2024-55655 正在被利用嗎?

低 — EPSS 為 0.1%,目前沒有觀察到大規模利用活動。

受影響套件(1)

• >= 2.0.0, < 3.6.0

CVSS 分數

參考連結(5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2024-55655
• PATCHgithub.com/sigstore/sigstore-python
• WEBgithub.com/sigstore/sigstore-python/commit/300b502ae99ebfaace124f1f4e422a6a669369cf
• WEBgithub.com/sigstore/sigstore-python/releases/tag/v3.6.0