CVE-2023-47122

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

Published Nov 10, 2023 CVSS 3.1 · 4.2 Medium EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2023-3067 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.
Github GHSA Github GHSA GHSA-xvrc-2wvh-49vc Gitsign's Rekor public keys fetched from upstream API instead of local TUF client.
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 3, 2024, 3:24 PM
Reserved
Oct 30, 2023, 7:57 PM
Status
Modified
Published
Nov 10, 2023, 10:15 PM
Modified
Jun 17, 2026, 6:32 AM