| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/sigstore/sigstore-go | < 1.2.0 | 1.2.0 |
| sigstore-go | < 1.2.0 | 1.2.0 |
What kind of vulnerability is it? Who is impacted?
A verifier configured with WithTransparencyLog(N>1) or WithSignedCertificateTimestamps(N>1) expected defense-in-depth against the compromise of a single log instance. However, threshold counting counted verified witnesses per-entry or per-validation-path rather than per-log-authority.
As a result, a single compromised transparency log could forge multiple entries with different indices, and a single compromised CT log could verify multiple times (either across multiple certificate chains or via multiple embedded SCTs), fully satisfying the multi-log threshold requirements and defeating the multi-log policy.
Note that this does not affect Cosign, as Cosign sets a threshold of 1.
Has the problem been patched? What versions should users upgrade to?
Upgrade to v1.1.5.
Is there a way for users to fix or remediate the vulnerability without upgrading?
There is no workaround, beyond relying on trusted logs.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free