- Veröffentlicht
- 05.11.2024 16:26
- Zuletzt geändert
- 03.03.2026
- EPSS (30 Tage)
- 0.1 %
- CVSS-Vektor
- CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
Beschreibung
Originaltext der Quelle, nicht übersetzt.
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.
Status beim Hersteller
SUSE stuft seine Produktlinien ein: 1 betroffen, 5 behoben.
Red Hat Trusted Artifact Signer
BetroffenFix zurückgestellt
gitsign-rhel9
SUSE Linux Enterprise Server 16.0
Behoben
govulncheck-vulndb-0.0.20250814T182633-160000.1.2
SUSE Linux Enterprise Server 16.1
Behoben
govulncheck-vulndb-0.0.20260916T180043-160100.1.1
SUSE Linux Enterprise Server for SAP applications 16.0
Behoben
govulncheck-vulndb-0.0.20250814T182633-160000.1.2
SUSE Linux Enterprise Server for SAP applications 16.1
Behoben
govulncheck-vulndb-0.0.20260916T180043-160100.1.1
openSUSE Tumbleweed
Behoben
govulncheck-vulndb-0.0.20241106T172143-1.1
Betroffene Pakete im beobachteten Stack
Red Hat:trusted_artifact_signer:1gitsign-rhel9kein Fix bekanntCVE-2024-51746
Weitere betroffene Pakete (8)
CVEsigstore/gitsignkein Fix bekanntCVE-2024-51746
Gogithub.com/sigstore/gitsign0.11.0GHSA-8pmp-678w-c8xx
Gogithub.com/sigstore/gitsign0.11.0GO-2024-3252
SUSE:Linux Enterprise Module for Package Hub 15 SP5govulncheck-vulndb0.0.20241112T145010-150000.1.17.1SUSE-SU-2024:4042-1
SUSE:Linux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20241112T145010-150000.1.17.1SUSE-SU-2024:4042-1
openSUSE:Leap 15.5govulncheck-vulndb0.0.20241112T145010-150000.1.17.1SUSE-SU-2024:4042-1
openSUSE:Leap 15.6govulncheck-vulndb0.0.20241112T145010-150000.1.17.1SUSE-SU-2024:4042-1
openSUSE:Tumbleweedgovulncheck-vulndb0.0.20241106T172143-1.1openSUSE-SU-2024:14470-1
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Lokal · Nutzerinteraktion) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.
Referenzen
- github.com/sigstore/gitsign/security/advisories/GHSA-8pmp-678w-c8xx
- www.suse.com/security/cve/CVE-2024-51746
- www.suse.com/support/security/rating/
- bugzilla.suse.com/1232903
- lists.suse.com/pipermail/sle-security-updates/2024-November/019840.html
- lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/OX53GMPD3MLNI5INQF5WZ3M4WW7BFHZC/
- nvd.nist.gov/vuln/detail/CVE-2024-51746
- github.com/sigstore/gitsign
- security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-51746.json
- access.redhat.com/security/cve/CVE-2024-51746
- bugzilla.redhat.com/show_bug.cgi
- www.cve.org/CVERecord