Vulnerabilities · 2023 · Sigstore
CVE-2023-47122
Sigstore Gitsign vulnerability
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.
Affected products
Gitsign. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Sigstore Gitsign runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/sigstore/gitsign/security/advisories/GHSA-xvrc-2wvh-49vc · Patch
- github.com/sigstore/gitsign/commit/cd66ccb03c86a3600955f0c15f6bfeb75f697236 · Patch
- github.com/sigstore/gitsign/pull/399 · Patch
- docs.sigstore.dev/about/threat-model/#sigstore-threat-model
- nvd.nist.gov/vuln/detail/CVE-2023-47122
- cve.org/CVERecord?id=CVE-2023-47122
More vulnerabilities in Sigstore products
CVE-2026-22703CVE-2024-45395CVE-2024-29903CVE-2024-29902CVE-2023-46737CVE-2022-36056CVE-2022-35930CVE-2022-35929All 10
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.