PatchPilot: remediate CVEs#5
Closed
moolen wants to merge 1 commit into
Closed
Conversation
Owner
Author
Agent Log Assets |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CVE remediation audit (moolen/logistis)
Scanned image:
ghcr.io/moolen/logistis:v0.1.1(120 findings)Rollout mode: Audit-only — no repository source files were modified (only this report).
human_intervention_needed: true until Dockerfile, module, and CI updates are implemented and re-scanned.Outcome
No further fixes possible in this audit rollout — the harness did not permit changing
Dockerfile,go.mod, or workflows. Partially remediated in the sense that the remediation path is identified; full remediation requires implementing the plan below and publishing a new image tag.Summary of actions taken
.patchpilot/input/cve-remediation.jsonand cross-checked the repository.Dockerfile(evidence:.github/workflows/ci.ymlusesdocker/build-push-actionwithcontext: .and default Dockerfile;Makefiledocker.builduses-fdefault / same context).DockerfileFROMchain: buildgolang:1.19, runalpine:3.14+apk add curl.go.mod(go 1.19) and direct/indirect dependency versions matching reported modules (e.g.golang.org/x/netpseudo-version,google.golang.org/protobuf v1.28.0,github.com/sirupsen/logrus v1.8.1).go build -o /tmp/logistis-webhook ./cmd/webhookandgo build -o /tmp/kubectl-blame ./cmd/kubectl-blame(success; binaries not committed).Validation steps performed
go versionon runner: go1.26.1 (toolchain differs from image’s go1.19.1; build still exercises module compile).go build -o /tmp/logistis-webhook ./cmd/webhook— passed.go build -o /tmp/kubectl-blame ./cmd/kubectl-blame— passed.govulncheck,docker build, and registry image re-scan not run (audit-only; no Dockerfile/dependency changes to validate end-to-end).Fixed findings
No repository files were changed in this audit-only rollout; nothing is remediated in-tree yet.
Grouped by where fixes would land (reference for follow-up):
Dockerfile: allstdlibscanner rows (Go 1.19.1 in image viaBASEIMAGE);libcrypto1.1/libssl1.1/curl/libcurl(Alpine 3.14 runtime +apk add curl).go.mod/go.sum:GHSA-*rows forgolang.org/x/net,golang.org/x/text,google.golang.org/protobuf,github.com/golang/glog,github.com/sirupsen/logrus..github/workflows/release.yml:stdlibalignment forkubectl-blamerelease builds (go1.19.1 tarball today).Safest remediation plan (for humans to implement)
Dockerfile— build stage (BASEIMAGE, defaultgolang:1.19)golangimage, list tags for the intended major/minor line and pick a tag that satisfies allstdlibfindings; several listed fixed versions require Go ≥ 1.25.8 / 1.26.1 for the newest CVEs — treat 1.26.1 or latest 1.26.x / 1.25.x patch in-family as the consolidation target after tag listing).CGO_ENABLED=0as today.Dockerfile— runtime (RUNIMAGE, defaultalpine:3.14)libcrypto1.1/libssl1.1) and old curl/libcurl matching scanner versions. Move to a supported Alpine (list tags; e.g. 3.20+). Newer Alpine uses OpenSSL 3 packages (different package names), which addresses the OpenSSL 1.1 CVEs by migration, not by pinning 1.1.1t-r*.curl/libcurlversion from the new Alpine release that meets the listed fixed versions, or remove curl from the image if not needed at runtime.go.mod/go.sumgo/toolchainwith the chosen Go version.golang.org/x/net(highest GHSA fix level cited is 0.38.0 / 0.36.0 among rows — use the maximum required),golang.org/x/text(≥ 0.3.8),google.golang.org/protobuf(≥ 1.33.0),github.com/golang/glog(≥ 1.2.4),github.com/sirupsen/logrus(≥ 1.8.3).k8s.io/*v0.25.1 may need a planned upgrade path compatible with newer Go; rungo mod tidyandgovulncheckafter bumps..github/workflows/release.ymlgoversiontarball URL from go1.19.1 to the same Go version used for production builds.Validation
go test ./...,go vet ./...(or project linter),govulncheck ./...,docker buildlocally, then re-scan the pushed image.Remaining findings (full table)
All rows: Status = not fixed in repo during this audit; Reason = audit-only constraint.
Notes
ghcr.io/moolen/logististo the rootDockerfilevia.github/workflows/ci.yml(docker/build-push-action, context.) andMakefile(docker buildxwithDOCKERFILE := Dockerfile).go.modand dependency versions match the scanner-reported module versions for Go modules. Localgo buildfor./cmd/webhookand./cmd/kubectl-blamesucceeded on the runner (Go 1.26.1 toolchain), confirming the tree compiles without changes..patchpilot/output.json), so registry tag listing, image rebuild, andgovulncheckagainst a remediated image could not be executed as part of a committed fix. Consolidating 120 scanner rows into a single remediation strategy requires choosing one minimum Go toolchain that satisfies the maximum fixed-version requirement across allstdlibCVEs (several 2025–2026 CVEs point at Go 1.25.x / 1.26.x lines), which implies a major jump from Go 1.19.1 and may force k8s.io/client-go and related upgrades.golangandalpineto pick non-guessed tags; AWS/ECR N/A here. Access to re-scanghcr.io/moolen/logistisafter changes. Maintainer decision on acceptable Alpine major version and whether to remove runtimecurlor replace with a minimal static binary-only image to shrink attack surface.Human intervention requested by agent: true
Agent Logs
cve-remediation stdout