CVE-2023-47122 json
Gitsign's Rekor public keys fetched from upstream API instead of local TUF client.
published 3y ago modified 4mo ago also GHSA-xvrc-2wvh-49vc , GO-2023-2332 , EUVD-2023-3067
- cvss
- 4.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/sigstore/gitsign 0.8.0
- sigstore gitsign 0.8.0
Is CVE-2023-47122 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/sigstore/gitsign | >=0.6.0, <0.8.0 |
0.8.0 |
Affected products
- sigstore gitsign
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
References
-
github.com
/sigstore/gitsign/pull/399
web, patch
-
github.com
/sigstore/gitsign/commit/cd66ccb03c86a3600955f0c15f6bfeb75f697236
web, patch
-
github.com
/sigstore/gitsign/security/advisories/GHSA-xvrc-2wvh-49vc
web, patch, vendor-advisory, advisory
-
docs.sigstore.dev
/about/threat-model/#sigstore-threat-model
web, product
-
nvd.nist.gov
/vuln/detail/CVE-2023-47122
advisory
-
github.com
/sigstore/gitsign
package
Sources
- CVE List CVE-2023-47122
- GitHub Advisory GHSA-xvrc-2wvh-49vc
- NVD CVE-2023-47122
- OSV GO-2023-2332
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.