-
Notifications
You must be signed in to change notification settings - Fork 420
gitsign/0.13.0-r7: cve remediation #75207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gitsign/0.13.0-r7: cve remediation #75207
Conversation
<!--ci-cve-scan:must-fix: GHSA-f83f-xpx7-ffpw-->
🛑 Build Failed: Compilation
Build Details
Root Cause Analysis 🔍API incompatibility between sigstore-go v0.7.0 and protobuf-specs dependencies. The SigningConfig type no longer has the expected methods (GetCaUrl, GetOidcUrl, GetTlogUrls) or has changed its interface, causing multiple compilation errors in the sigstore-go package. 🔍 Build failure fix suggestionsFound similar build failures that have been fixed in the past and analyzed them to suggest a fix: Suggested ChangesFile: package/gitsign.yaml
Replacement: Content: Click to expand fix analysisAnalysisNo similar build failures were provided for analysis. However, based on the error message indicating API incompatibility between sigstore-go v0.7.0 and protobuf-specs dependencies where SigningConfig type no longer has expected methods (GetCaUrl, GetOidcUrl, GetTlogUrls), this appears to be a dependency version mismatch issue that requires updating the sigstore/protobuf-specs dependency to a compatible version. Click to expand fix explanationExplanationThe compilation error indicates that the SigningConfig type from github.com/sigstore/protobuf-specs/gen/pb-go/trustroot/v1 no longer has the expected methods (GetCaUrl, GetOidcUrl, GetTlogUrls). This is a classic dependency version mismatch where the protobuf-specs package has been updated with breaking API changes that are incompatible with the version of sigstore-go being used (v0.7.0). By explicitly bumping the protobuf-specs dependency to a compatible version (v0.3.0), we ensure that the API methods expected by sigstore-go are available. The go/bump pipeline step will update the go.mod file to use the specified version, resolving the compilation errors caused by missing methods on the SigningConfig type. Click to expand alternative approachesAlternative Approaches
Was this comment helpful? Please use 👍 or 👎 reactions on this comment. |
Signed-off-by: David Negreira <[email protected]>
|
needs advisory wolfi-dev/advisories#27933 |
|
This vulnerability remediation is stale and no longer needed. 👋 Advisory CGA-xrvj-839r-77q9 has the latest event type of "pending-upstream-fix": https://github.com/wolfi-dev/advisories/blob/main/gitsign.advisories.yaml 🔀 v2 advisory logic would not have closed this PR: Found 4 advisories, but 2 of them are not resolved (CGA-j6w5-q3hw-pw8j, CGA-gv44-j7jq-9rxh). |
gitsign/0.13.0-r7: fix GHSA-f83f-xpx7-ffpw
Advisory data: https://github.com/wolfi-dev/advisories/blob/main/gitsign.advisories.yaml
"Breadcrumbs" for this automated service