Skip to content

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

Moderate severity GitHub Reviewed Published Nov 10, 2023 in sigstore/gitsign • Updated Nov 14, 2023

Package

gomod github.com/sigstore/gitsign (Go)

Affected versions

>= 0.6.0, < 0.8.0

Patched versions

0.8.0

Description

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 sigstore/gitsign#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

References

@wlynch wlynch published to sigstore/gitsign Nov 10, 2023
Published by the National Vulnerability Database Nov 10, 2023
Published to the GitHub Advisory Database Nov 14, 2023
Reviewed Nov 14, 2023
Last updated Nov 14, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N

EPSS score

0.090%
(40th percentile)

Weaknesses

CVE ID

CVE-2023-47122

GHSA ID

GHSA-xvrc-2wvh-49vc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.