-
Notifications
You must be signed in to change notification settings - Fork 419
undock/0.11.0-r0: cve remediation #77737
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
undock/0.11.0-r0: cve remediation #77737
Conversation
<!--ci-cve-scan:must-fix: GHSA-cgrx-mc8f-2prm-->
🛑 Build Failed: Compilation
Build Details
Root Cause Analysis 🔍Missing or incompatible securejoin package dependency - the OpenInRoot and Reopen functions are undefined, indicating either the securejoin package is not available or is an incompatible version that doesn't expose these functions 🔍 Build failure fix suggestionsFound similar build failures that have been fixed in the past and analyzed them to suggest a fix: Similar PRs with fixes
Suggested ChangesFile: undock.yaml
Replacement: Content: Click to expand fix analysisAnalysisLooking at the three similar fixes, there's a clear pattern: all failures involve the same undefined functions (securejoin.OpenInRoot and securejoin.Reopen) from the cyphar/filepath-securejoin package. The successful fixes consistently use one of two approaches: 1) Adding a replace directive to pin filepath-securejoin to v0.5.1 (seen in both podman fixes), or 2) Upgrading to a newer upstream version that includes compatible dependencies (seen in the buildah fix). The replace directive approach appears more reliable as it directly addresses the version incompatibility by forcing the use of a known-good version of the securejoin package. Click to expand fix explanationExplanationThe fix works by adding a replace directive that forces the Go module system to use a specific version (v0.5.1) of the cyphar/filepath-securejoin package, which is known to contain the OpenInRoot and Reopen functions that the code is trying to use. This approach directly addresses the root cause of the compilation error - the vendored code expects these functions to exist, but the current version of the securejoin package in the dependency tree doesn't provide them. The replace directive overrides the normal dependency resolution and ensures the compatible version is used. This is the same solution that successfully fixed the identical error in the podman package twice, making it a proven approach for this specific issue. Click to expand alternative approachesAlternative Approaches
Was this comment helpful? Please use 👍 or 👎 reactions on this comment. |
|
We have advisory for this and can confirm we can't able to mitigate at this point:
|
|
This vulnerability remediation is stale and no longer needed. 👋 Advisory CGA-v4gx-5w7w-pqgp has the latest event type of "pending-upstream-fix" View with: |
|
This vulnerability remediation is stale and no longer needed. 👋 Advisory CGA-43vh-3w7c-3gxq has the latest event type of "PENDING_UPSTREAM_FIX" View with: |
undock/0.11.0-r0: fix GHSA-cgrx-mc8f-2prm
Advisory data: https://github.com/wolfi-dev/advisories/blob/main/undock.advisories.yaml
"Breadcrumbs" for this automated service
Inspected git repositories: https://github.com/crazy-max/[email protected]