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

CVE-2023-47122 → View on GitHub ↗ View on CVE.org ↗ View on NVD ↗

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

Basic information

Type
reviewed
Severity
medium
Advisory on GitHub
Open advisory ↗
Repository advisory
Open repository advisory ↗
Source code
Browse source ↗
Published (advisory)
2023-11-14 20:31:23 UTC
Updated
2023-11-14 20:31:24 UTC
GitHub reviewed
2023-11-14 20:31:23 UTC
NVD published
2023-11-10

EPSS Score

Score Percentile
0.09% 25.58%

CVSS Scores

Base score Version Severity Vector
4.2 3.1 —
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.

Identifiers

Type Value
GHSA GHSA-xvrc-2wvh-49vc ↗
CVE CVE-2023-47122 ↗

CWEs

CWE id Name
CWE-347 Improper Verification of Cryptographic Signature

Credits

  • adityasaky (finder)

Affected packages (1)

Vulnerable version ranges and first patched releases as published by GitHub.

Ecosystem Package Vulnerable range First patched Vulnerable functions
go github.com/sigstore/gitsign >= 0.6.0, < 0.8.0 0.8.0 —

References

cvelogic Threat Intelligence