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
beschreibt (1)
Zugehörige CVEs.
| ID | Schweregrad | ausnutzbar | ||
|---|---|---|---|---|
| CVE-2023-47122US | medium5.3 | — | ||
Gitsign is software for keyless Git signing using Sigstore. In versions of gitsign starting with 0.6.0 and prior to 0.8.0, Rekor public keys were fetched via the Rekor API, instead… | ||||
Referenzen
Externe Belege — Patches, Meldungen, Analysen.
- https://docs.sigstore.dev/about/threat-model/#sigstore-threat-modelWEB
- https://github.com/sigstore/gitsignPACKAGE
- https://github.com/sigstore/gitsign/commit/cd66ccb03c86a3600955f0c15f6bfeb75f697236WEB
- https://github.com/sigstore/gitsign/pull/399WEB
- https://github.com/sigstore/gitsign/security/advisories/GHSA-xvrc-2wvh-49vcWEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-47122ADVISORY
Advisories wie diese benennen die exponierten Produkte, die Angreifer auf Ihrer Angriffsfläche ins Visier nehmen. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan