fix(snyk): remediate high-and-above vulnerabilities blocking PRIM-100/cli-provenance-attestations-ff-9.19.0 - #7128
Open
prodsec-github-automation wants to merge 4 commits into
Conversation
…[PRIM-100] Bump snyk-docker-plugin to ^9.19.0 (adds provenance attestation extraction and the vcs.source fallback for buildConfigSourceUri) and gate the provenanceMetadata fact behind the surfaceProvenanceAttestations feature flag in filterDockerFacts, mirroring the allowNewContainerFacts pattern. Pinned to 9.19.0 rather than 9.20.0 deliberately. 9.20.0 adds a best-effort provenance fetch to the image's registry (snyk/snyk-docker-plugin#891). The plugin handles a failed fetch and the scan completes, but the CLI records the failed request as a command error and appends a second JSON object after the result, which breaks JSON.parse in container.spec.ts. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ture flag Provenance attestations should be surfaced unconditionally, so drop the `surfaceProvenanceAttestations` gating this PR originally introduced. `shouldFilterFact` is a denylist and `provenanceMetadata` is not in it, so removing the special case is sufficient for the fact to always pass through. The snyk-docker-plugin 9.19.0 bump is retained -- that is what produces the provenance facts. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
`^9.19.0` allows 9.20.x, which reintroduces the double-JSON-output problem described in the PR (CLIA-1576). The lockfile pinned 9.19.0 so `npm ci` was safe, but any lockfile regeneration would have silently floated to 9.20.x. Exact pinning matches the convention already used for snyk-go-plugin, snyk-gradle-plugin and snyk-module in this file. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…Source gate Applied by snyk fix --agentic via the Snyk ProdSec CircleCI orb, from PRIM-100/cli-provenance-attestations-ff-9.19.0 at e6545e5. These changes are generated. Review them before merging.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
PR Reviewer Guide 🔍
|
bdemeo12
force-pushed
the
PRIM-100/cli-provenance-attestations-ff-9.19.0
branch
from
August 13, 2026 17:16
e6545e5 to
0c444b0
Compare
Base automatically changed from
PRIM-100/cli-provenance-attestations-ff-9.19.0
to
main
August 14, 2026 08:30
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
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.
Snyk agentic fix
The Snyk Open Source quality gate blocked
PRIM-100/cli-provenance-attestations-ff-9.19.0. This branch was produced bysnyk fix --agentic, working on vulnerabilities at or above high severity — the same threshold that gate is configured with.3 of 3 fixed.
Fixed
cliv2/go.modv5.19.1tov5.19.2. The release contains security updates and bug fixes. Key Changes: - Updates to dependencies such asgolang.org/x/cryptoandgolang.org/x/netfor security purposes. [1] - A security fix to reject path traversal in reference names. [1] - A bug fix for handling backslashes in index entries on Windows. [1] There are no documented breaking API changes in this patch release. The changes are focused on improving security and fixing platform-specific bugs. Source: GitHub Release Notescliv2/go.modstorage/filesystem/dotgitpackage is the introduction of stricter validation to reject path traversal in reference names. While this is a security enhancement, it is a behavioral change that could cause issues if an application was inadvertently relying on the previous, less strict validation. This change elevates the risk to medium, as it may require verification. Other changes include dependency updates and a fix for handling backslashes on Windows. Recommendation: Verify that any logic creating or handling git reference names does not rely on paths that could now be rejected as traversal attempts.package.jsonThis is not necessarily a complete fix. The build on this pull request runs the same quality gate that blocked
PRIM-100/cli-provenance-attestations-ff-9.19.0, so its result — not this description — is the verdict on what is left.Changes
Snyk ProdSec orb · build 635742 · model
claude-opus-4-8