Skip to content

Resolve scanner dependency advisories before adoption #5553

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem and impact

The public kubevuln scanner release reports reachable dependency advisories in both executable entrypoints. A functional scanner repair therefore needs a separate security disposition before adoption; a verified signature does not establish that result.

An audit of unmodified v0.3.571 reproduces eight advisory records across three modules. Some records cover broad legacy modules, so their reported count must not be presented as eight proven exploitable defects. The HTTP dependency has a published fixed release; the existing upstream RAR-decoder issue remains separately tracked by the project.

Acceptance criteria

  • Establish a reproducible source and actual published-binary baseline with the public advisory database.
  • Apply supported dependency corrections without changing scanner capabilities, discarding results or suppressing advisories.
  • Analyze remaining records against their upstream advisories and real call paths; retain unresolved findings as blockers.
  • Validate both scanner entrypoints and the existing functional regression suite, with an independent review of the proposed head.
  • Adopt only a reviewed, tested, signed immutable artifact, then prove complete current-image result coverage through the protected deployment path.

This is a prerequisite for the scanner adoption in #5403, under the platform roadmap #2043. Detailed audit and runtime evidence stays in private operator evidence. Upstream dependency coordination remains with the upstream maintainers; no unrelated Syft or Grype version change is proposed.

Activity

  1. self-assigned this
    on Oct 29, 2026
  2. moved this to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Oct 29, 2026
  3. added a commit that references this issue on Oct 29, 2026
  4. devantler commented on Oct 29, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The latest published upstream scanner reproduces the dependency audit blocker. A manifest pin cannot change embedded executable dependencies, and no existing portfolio-owned artifact supplies the correction. The sufficient source change is a small upstream dependency update; the public project and its contribution policies have been checked, and its PR template is available.

    The prepared change updates only the HTTP dependency and its Go-generated checksums. Both entrypoints build; the complete source race suite, vet and pinned lint pass. The target's full test command passes with its four existing skips explicitly retained as unexecuted coverage. Source and both executable audits remove the HTTP records while preserving three other unresolved records. A clean overall audit and deployment acceptance have not been established, so the image-adoption hold remains.

  5. added a commit that references this issue on Oct 29, 2026
  6. devantler commented on Oct 29, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The minimal HTTP dependency correction is offered upstream as kubescape/kubevuln#1218, Ready for Review at signed head 8ec68b4582dbb185b1b9ca8d827ec468d182f7e3. The target template and published body are now verified through the required write gate. Local validation is complete with the declared integration-test skips; hosted fork workflows require upstream maintainer approval, so no hosted success is claimed.

    The remaining dependency records and protected artifact/adoption acceptance remain unresolved. This issue and the scanner adoption stay open; the upstream review handoff does not establish platform recovery.

  7. devantler commented on Oct 29, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The HTTP dependency correction kubescape/kubevuln#1218 merged on 29 October after upstream approval at its exact proposed head. The resulting upstream revision is 3f1c4edc7a5a667ffba357122add316900daacd3.

    The post-merge executable audit still fails with three remaining advisory records. This confirms partial upstream delivery, without establishing a clean audit, an accepted published artifact or platform adoption. The remaining analysis and protected adoption criteria above remain open; #5403 and its delivery PR stay held.

  8. devantler commented on Oct 29, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The existing upstream stack upgrade now covers the Syft, stereoscope and container-registry dependency changes, so a duplicate proposal is unnecessary. At 6462921584b809d48e76f986280d9f336d9e912e, native build, lint and Basic-Test checks pass. The upstream review still requests the fixed Syft fork, and the proposed upgrade retains other dependency-audit findings.

    This is static source and native-check evidence only. The branch has not been executed locally, no new scanner artifact has been accepted, and #5405 stays held. After the upstream repair lands, independently audit both published executables and validate current-image scan coverage through protected deployment before closing this issue.

  9. devantler commented on Nov 2, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Upstream moved today, but the audit is still red, so this stays open and #5405 stays held. Read on 2 November from public upstream records only. I did not build, run or pull the scanner.

    kubescape/kubevuln#1224 merged at 07:11 UTC and v0.3.575 followed at 15:08 UTC, with Grype v0.121.0 and Syft v1.55.0.

    Check 29 October v0.3.575 today
    Upstream govulncheck Fails, 3 records Fails, 2 records from 1 module
    Remaining records GO-2026-4887 and GO-2026-4883, both on github.com/docker/docker v28.5.2

    What the two records are. Both describe Moby plugin features: an AuthZ plugin bypass and a plugin privilege check. Neither record lists affected symbols, and both mark every version of docker/docker as affected with no fix on that module path. The only listed fix is github.com/moby/moby/v2 2.0.0-beta.8. So no version bump of this module can clear them. A disposition from real call paths looks like the route, and it has not been done yet.

    Three things this read does not establish:

    • Other entrypoints. Upstream's job stops at the first failure, on kubevuln. The tag also has cmd/cli and cmd/sbom-scanner, so this result does not cover them.
    • The published image. That job scans a binary it built, not the released image.
    • Reachability. The report lists 17 docker-credential-helpers client symbols under these records, which the records themselves do not name. I have not traced why.

    Adoption is now bigger than the #5405 pin:

    • fix(kubescape): restore vulnerability summary references #5405 still pins v0.3.566, so it needs a new pin.
    • The v0.3.575 notes say SBOMs built with this Syft need kubescape/storage v0.0.382 to decode new source types and keep new package metadata. The platform runs its own storage build based on v0.0.297, so a scanner bump alone risks storing incomplete SBOMs. The storage build has to move first or together with it. I did not test this.

    Next: trace how docker/docker is imported, audit the published image's executables, then decide the scanner and storage order.

  10. devantler commented on Nov 2, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Reachability trace, v0.3.575 source at cbaa9d5. go list -deps on each entrypoint, without building or running anything.

    Entrypoint docker/docker packages linked moby/moby packages linked
    cmd/http, cmd/sbom-scanner api/types/versions, api/types/filters, api/types/registry api/types/* and client/*
    cmd/cli None None

    So neither serving entrypoint links the Docker daemon, its authorization middleware or its plugin manager. Both records describe those features and carry no symbol list, so govulncheck can only match them at module level. That supports a documented not-affected disposition for these two records, but it is my reading of the advisory summaries plus this package list, not a confirmed upstream statement. I have not recorded that disposition or cleared the blocker. It covers source at the tag, and the published image audit remains open. The earlier note about 17 docker-credential-helpers symbols is still unexplained.

  11. 8 remaining items

  12. devantler commented on Nov 2, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The remaining audit attribution failure now reproduces with a small standalone program using only public dependencies. Both the existing auditor and its current stable release assign Docker-module advisories to a separate module with an overlapping path prefix.

    The matching is implemented inside the upstream Go auditor, and there is no sufficient Platform configuration alternative that repairs that logic while preserving the binary-audit gate. I am reporting the reproducible tool defect on its canonical golang/go tracker under that project's vulnerability-management issue form. The official audit remains enforced, and scanner adoption stays held until the attribution problem is resolved.

  13. devantler commented on Nov 2, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The defect reported in golang/go#82780 is in the auditor owned by golang/vuln. A minimal two-file correction now passes the canonical source's full test suite, affected-package race tests, vet, and the unchanged public reproduction.

    The current released auditor still reproduces the defect; a Platform configuration change cannot repair its module-matching implementation while preserving the binary-audit gate. The necessary upstream code contribution will therefore target golang/vuln using its supported GitHub contribution process. Scanner adoption remains held until a reviewed, corrected auditor and the required scanner artifact are available.

  14. devantler commented on Nov 2, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The storage compatibility and dependency repair in #5776 has passed current-head validation and review and is in the protected merge queue. Its immutable image is not published or adopted yet.

    The scanner dependency follow-up is kubescape/kubevuln#1226. Its ordinary binary audit still fails on the unchanged release and the proposed update. The reproduced module-attribution defect is golang/go#82780; golang/vuln#15 is now ready for upstream review after local validation and the passing CLA check. Experimental auditor binaries have not replaced the normal acceptance gate. The scanner PR and runtime adoption remain held; this issue stays open.

  15. added 5 commits that reference this issue on Nov 3, 2026
  16. devantler commented on Nov 3, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The storage prerequisite has advanced: #5776 merged and its publication workflow succeeded. I independently verified the immutable image signature and provenance, then extracted and audited both shipped executables with the official released auditor; both pass.

    Runtime adoption is proposed in draft #5808. Local manifest and authorization validation pass, including the complete-object ledger update required for the image pin. Current-head hosted checks, independent review, protected deployment and complete current-image result readback remain required.

    The scanner upgrade remains held on its separately tracked dependency and ordinary-auditor gates. Neither this publication nor the adoption draft closes #5553 or establishes complete platform security.

  17. devantler commented on Nov 3, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The scanner dependency correction kubescape/kubevuln#1226 merged at 06:45 UTC on 3 November as cf9ff2edf174e41ad6ac2712e1dde7e1a046a1c5. The latest published scanner release is still v0.3.575, so that source delivery has not yet produced an accepted replacement artifact.

    I also independently checked the latest official Go auditor: v1.9.0, with its module checksum and public tag bound to the canonical Go repository. It still reproduces the module-prefix attribution defect on the unchanged public reproduction. The upstream Gerrit review remains open without maintainer feedback. This confirms the blocker against the current released auditor; no experimental auditor was substituted and no binary-audit gate was relaxed.

    Storage adoption #5808 now has current-head green checks and clean independent review and is accepted into the protected merge queue. Actual runtime adoption, the newly corrected scanner publication and complete current-image results remain outstanding; this issue and #5405 stay open.

  18. devantler commented on Nov 12, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Re-checked 12 November: the upstream release now exists. kubescape/kubevuln published v0.3.578 and v0.3.580 on 4 November. GitHub's compare API shows v0.3.580 is 5 commits ahead of the correction from kubescape/kubevuln#1226 (cf9ff2ed) and 0 behind it, so that release contains it.

    That ends the wait recorded on 3 November. The next step is the same check as before, on the new release: confirm its dependency advisories are resolved with the official Go auditor, then verify the published artifact before any reviewed adoption. #5405, parked on this issue, resumes after that. I did not check v0.3.580's advisories or artifact in this pass, and nothing was adopted or changed.

  19. devantler commented on Nov 12, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    v0.3.580 audited and verified. Not adoptable yet, because three reachable advisories have fixes that this release lacks. Upstream is applying exactly those fixes now, so this waits for that release.

    Check Result
    Artifact The v0.3.580 multi-arch digest verifies with Sigstore keyless signing. The signer is Kubescape's shared release workflow, run for repository kubescape/kubevuln at workflow commit add39ff8, which is exactly the v0.3.580 tag commit. Both shipped layers matched their registry digests.
    Earlier baseline The HTTP-dependency record from the v0.3.571 baseline is gone; kubescape/kubevuln#1226 is in this release.
    Official Go auditor, v1.9.0 (DB of 11 Nov) Source mode and both shipped binaries (the HTTP service and the SBOM scanner) give identical results: five reachable advisory families. The binaries carry the Go 1.26.10 toolchain.
    Three families have published fixes Two compression libraries and the Go standard library's HTTP package. Each has a fixed release this build does not use.
    Two families have no fix Archive parser panic: used only by the SBOM generator's .deb-archive cataloger, which runs inside its task executor's per-cataloger panic recovery. A crafted package archive can cost that one cataloger's results for that image; it cannot crash the scanner. Container-engine records: reached only through package initialisers of the engine's client library. The affected engine-side authorization and plugin code is never executed by the scanner. Both are retained as recorded residual risk, not suppressed.
    Auditor defect The engine records are also attributed to a second module whose path shares the engine module's prefix. This is the module-prefix misattribution recorded on 3 November, still present in v1.9.0, and is not counted as a separate finding.

    Next: kubescape/kubevuln#1245, opened today by an upstream maintainer, raises exactly the two compression libraries and the Go toolchain to their fixed releases. It is open and not yet merged or released. When a release containing it is published, repeat this check on that release (artifact binding, both binaries, the two no-fix dispositions). Then resume adoption through #5405, which is parked on this issue.

    Nothing was adopted or changed in the cluster. Detailed advisory records and traces stay in private operator evidence.

  20. devantler commented on Nov 16, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The scanner was upgraded without waiting for this issue. On 13 November, the Renovate chart update #6221 (kubescape-operator 1.42.0) went through the normal protected path. Production now runs that chart's default kubevuln, v0.3.578. Nothing tied the chart's own default image to this issue, so the "before adoption" hold here did not apply to it.

    What this changes:

    I have not changed anything in production or rolled back the chart. Rolling back would bring back the older default image and the reference bug #5403 tracks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Fields

No fields configured for Security.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions