Upgrade anchore/scan-action to v7.3.2 to fix CVE-2025-59250 false positive#493
Merged
Upgrade anchore/scan-action to v7.3.2 to fix CVE-2025-59250 false positive#493
Conversation
The pinned scan-action (v5) bundled Grype v0.85.0 which has a false-positive for CVE-2025-59250 on mssql-jdbc due to Microsoft's non-standard version metadata. This was fixed in Grype v0.104.1+ (anchore/grype#3034). Upgrading to scan-action v7.3.2 which bundles Grype v0.107.1 resolves the false positive at the scanner level. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Organization UI Review profile: CHILL Plan: Pro Disabled knowledge base sources:
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdates the Grype SBOM scan GitHub Action from v5 to v7.3.2 in the reusable vulnerability scan workflow. The change maintains all other parameters and only modifies the container image tag reference. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
anchore/scan-actionfrom v5 (Grype v0.85.0) to v7.3.2 (Grype v0.107.1)liquibase-secureimageContext
PR #492 extended the
.trivyignoreexpiration which fixed the Trivy scans, but the Grype scan still reportsgrype_vulns: 1because.trivyignoreonly applies to Trivy.The root cause — Grype's incorrect version comparison of mssql-jdbc
13.2.1vs13.2.1.jre11— was fixed upstream in anchore/grype#3034 (merged Nov 2025, shipped in v0.104.1). The workflow was pinned to scan-action v5 which bundles Grype v0.85.0, predating the fix.Failing run: #22321625392
Test plan
grype_vulns: 0in scan output🤖 Generated with Claude Code