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

TRUNG BÌNH 5.3CVE-2023-47122 · GHSA-xvrc-2wvh-49vc · GO-2023-2332 · Công bố 10/11/2023 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2023-47122 là lỗ hổng mức TRUNG BÌNH (CVSS 5.3) ảnh hưởng github.com/sigstore/gitsign, gitsign (sigstore).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.37%, cao hơn 30.9% các lỗ hổng khác.
Cách xử lý: cập nhật lên 0.8.0 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
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`

Mô tả

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

Mô tả của 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.