Vulnerability · Published Nov 10, 2023 · Assigned by GitHub_M

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

Medium 4.2

In plain English

A medium-severity security flaw in gitsign from sigstore. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 31% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)4.2Medium
Exploit odds (30 days)0.4%top 69.0% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/sigstore/gitsign0.8.0GHSA-xvrc-2wvh-49vc
Gogithub.com/sigstore/gitsign0.8.0GO-2023-2332

Affected products (as reported)

VendorProductVersions
sigstore gitsign >= 0.6.0, < 0.8.0

Weakness: CWE-347 · Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N

References