Ecosyste.ms: Advisories

An open API service providing security vulnerability metadata for many open source software ecosystems.

Security Advisories: GSA_kwCzR0hTQS14dnJjLTJ3dmgtNDl2Y84AA3Ht

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

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

Permalink: https://github.com/advisories/GHSA-xvrc-2wvh-49vc
JSON: https://advisories.ecosyste.ms/api/v1/advisories/GSA_kwCzR0hTQS14dnJjLTJ3dmgtNDl2Y84AA3Ht
Source: GitHub Advisory Database
Origin: Unspecified
Severity: Moderate
Classification: General
Published: about 1 year ago
Updated: about 1 year ago


CVSS Score: 4.2
CVSS vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N

Identifiers: GHSA-xvrc-2wvh-49vc, CVE-2023-47122
References: Repository: https://github.com/sigstore/gitsign
Blast Radius: 2.0

Affected Packages

go:github.com/sigstore/gitsign
Dependent packages: 2
Dependent repositories: 3
Downloads:
Affected Version Ranges: >= 0.6.0, < 0.8.0
Fixed in: 0.8.0
All affected versions: 0.6.0, 0.7.0, 0.7.1
All unaffected versions: 0.1.0, 0.1.1, 0.2.0, 0.3.0, 0.3.1, 0.3.2, 0.4.0, 0.4.1, 0.5.0, 0.5.1, 0.5.2, 0.8.0, 0.8.1, 0.9.0, 0.9.1, 0.10.0, 0.10.1, 0.10.2, 0.11.0