Gitsign's Rekor public keys fetched from upstream API instead of local TUF client.

中 5.3CVE-2023-47122 · GHSA-xvrc-2wvh-49vc · GO-2023-2332 · 10/11/2023 公開 · 17/06/2026 更新

要点

CVE-2023-47122 は github.com/sigstore/gitsign, gitsign (sigstore) に影響する深刻度「中」 (CVSS 5.3) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.37%（全脆弱性の 30.9% より高い）。
対処：0.8.0 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/sigstore/gitsign Go	`≥ 0.6.0, < 0.8.0`	`0.8.0`
gitsign sigstore	`≥ 0.6.0, < 0.8.0`	`0.8.0`

概要

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

NVD の説明

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 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 unaffected. This issue was fixed in v0.8.0. No known workarounds are available.