Upstream information
Description
Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. gitsign may select the wrong Rekor entry to use during online verification when multiple entries are returned by the log. gitsign uses Rekor's search API to fetch entries that apply to a signature being verified. The parameters used for the search are the public key and the payload. The search API returns entries that match either condition rather than both. When gitsign's credential cache is used, there can be multiple entries that use the same ephemeral keypair / signing certificate. As gitsign assumes both conditions are matched by Rekor, there is no additional validation that the entry's hash matches the payload being verified, meaning that the wrong entry can be used to successfully pass verification. Impact is minimal as while gitsign does not match the payload against the entry, it does ensure that the certificate matches. This would need to be exploited during the certificate validity window (10 minutes) by the key holder.SUSE information
Overall state of this security issue: Resolved
This issue is currently rated as having low severity.
| CNA (GitHub) | |
|---|---|
| Base Score | 1.8 |
| Vector | CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| Attack Vector | Local |
| Attack Complexity | High |
| Attack Requirements | Present |
| Privileges Required | None |
| User Interaction | Active |
| Vulnerable System Confidentiality Impact | None |
| Vulnerable System Integrity Impact | Low |
| Vulnerable System Availability Impact | None |
| Subsequent System Confidentiality Impact | None |
| Subsequent System Integrity Impact | None |
| Subsequent System Availability Impact | None |
| CVSSv4 Version | 4.0 |
SUSE Security Advisories:
- SUSE-SU-2024:4042-1, published 2024-11-22T10:44:15Z
- openSUSE-SU-2024:14470-1, published Fri Nov 8 18:50:07 2024
List of released packages
| Product(s) | Fixed package version(s) | References |
|---|---|---|
| SUSE Linux Enterprise Module for Package Hub 15 SP5 |
| Patchnames: SUSE-SLE-Module-Packagehub-Subpackages-15-SP5-2024-4042 |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 |
| Patchnames: SUSE-SLE-Module-Packagehub-Subpackages-15-SP6-2024-4042 |
| openSUSE Leap 15.5 |
| Patchnames: openSUSE-SLE-15.5-2024-4042 |
| openSUSE Leap 15.6 |
| Patchnames: openSUSE-SLE-15.6-2024-4042 |
| openSUSE Tumbleweed |
| Patchnames: openSUSE-Tumbleweed-2024-14470 |
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
| Product(s) | Source package | State |
|---|---|---|
| Products under general support and receiving all security fixes. | ||
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | govulncheck-vulndb | Released |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | Released |
| openSUSE Leap 15.5 | govulncheck-vulndb | Released |
| openSUSE Leap 15.6 | govulncheck-vulndb | Released |
SUSE Timeline for this CVE
CVE page created: Tue Nov 5 22:00:35 2024CVE page last modified: Fri Nov 22 15:56:48 2024