github.com/sigstore/gitsign
Affected
- introduced
0.6.0, fixed0.8.0(semver)
Fixed versions
0.8.0
Fix
- Fixed version
0.8.0go get github.com/sigstore/[email protected]
Advisory
Also known as: CVE-2023-47122, GO-2023-2332
Gitsign's Rekor public keys fetched from upstream API instead of local TUF client.
Impact
In certain versions of gitsign, Rekor public keys were fetched via the Rekor API, instead of through the local TUF client. If the upstream Rekor server happened to be compromised, gitsign clients could potentially be tricked into trusting incorrect signatures.
There is no known compromise the default public good instance (rekor.sigstore.dev) - anyone using this instance is unlikely to be affected.
Patches
This was fixed in v0.8.0 via https://github.com/sigstore/gitsign/pull/399
Workarounds
n/a
References
_Are there any links users can visit to find out more?_
https://docs.sigstore.dev/about/threat-model/#sigstore-threat-model
Medium Basis: The source's own band: MODERATE
0.6.0, fixed 0.8.0 (semver)0.8.0
0.8.0go get github.com/sigstore/[email protected]Fix 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: GitHub Advisory Database (reviewed advisories) · CC BY 4.0