Add a repeatable script for reproducing customer CVE scans - #2093
Draft
NickJosevski wants to merge 1 commit into
Draft
Add a repeatable script for reproducing customer CVE scans#2093NickJosevski wants to merge 1 commit into
NickJosevski wants to merge 1 commit into
Conversation
Reproducing a customer CVE report meant re-deriving the same steps every time. Customers scan the files on their deployment targets. They do not scan this repo or the NuGet graph. The surfaces give different answers. dotnet list package --vulnerable walks the NuGet graph and reports build-time reference shims that contribute no runtime assembly. No customer scanner ever sees those shims. The discrepancy has been a recurring source of confusion. The script downloads the published consolidated package, extracts every flavour and RID, prints the bundled .NET runtime version, then scans with Trivy and Grype. Two databases are used deliberately. Customer scanners disagree with each other and one tool is not a baseline. Results separate total matches from distinct CVEs. The same finding repeats across roughly 43 deps.json files. A customer reporting 42 vulnerabilities is routinely reporting one. Calamari version is usually the answer. Measured 2026-08-01. Version 2025.3.417 has 9 distinct CVEs and bundles .NET 6.0.36. That runtime reached end of life in November 2024. Version 2026.3.508 has 1 and bundles 8.0.29. The README covers reading results. It also records two traps found while building the script. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
NickJosevski
force-pushed
the
nj/cve-scan-script
branch
from
August 4, 2026 07:51
dc4c77b to
5b2cf0c
Compare
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.
Background
Reproducing a customer CVE report meant re-deriving the same steps every time.
Customers scan the files on their deployment targets. They do not scan this repo or the NuGet graph. The surfaces give different answers.
dotnet list package --vulnerablewalks the NuGet graph and reports build-time reference shims that contribute no runtime assembly. No customer scanner ever sees those shims. The discrepancy has caused repeated confusion.Results
Adds
scripts/scan-calamari-cves/scan.sh.The script downloads the published consolidated package, extracts every flavour and RID, prints the bundled .NET runtime version, then scans with Trivy and Grype. Two databases are used because customer scanners disagree with each other. One tool is not a baseline.
Results separate total matches from distinct CVEs. The same finding repeats across roughly 43
deps.jsonfiles. A customer reporting 42 vulnerabilities is routinely reporting one.Calamari version is usually the answer. Measured 2026-08-01:
2025.3.4172026.3.508The README covers how to read results. It also records two traps found while building the script.
How to review this PR
General quality.