CVE-2023-471224.2MediumCWE-347

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

sigstore · gitsign

Affected: sigstore gitsign · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.4%probability of exploitation in the next 30 days

39th percentile

050100

Higher than 39% of scored CVEs

4.2MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

sigstore · gitsign>= 0.6.0, < 0.8.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Verification of Cryptographic Signature · Cryptography
Vendor: sigstore
Published: November 2023
Band: Unlikely (under 1%), November 2023

CoverageNo articles yet

No CyberSIXT article names CVE-2023-47122 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.