Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vulnerabilities identified in a scan using Trivy can differ depending on whether an image or an SBOM is used. #4302

Closed
afdesk opened this issue May 10, 2023 Discussed in #4221 · 0 comments · Fixed by #4306
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@afdesk
Copy link
Contributor

afdesk commented May 10, 2023

Details

We lose case-sensitivity in PURL used in SBOM and it leads to the wrong results.

Discussed in #4221

Originally posted by genos1998 May 8, 2023
Initially I scanned an open source image for vulnerabilities using the below cmd:
trivy image argoproj/argocd --format=cyclonedx -o argo-trivy-issue-imageScan.json --scanners vuln --timeout 60m

And then I performed another vulnerability scan using the sbom which was generated using the above cmd
trivy sbom argo-trivy-issue-imageScan.json --format=cyclonedx -o argo-trivy-issue-sbomScan.json --scanners vuln

After thorough analysis I found out that there was a difference of 3 vulnerabilities between them:
"CVE-2022-21235", "GHSA-xg2h-wx96-xgxr", "CVE-2021-4238"

Shouldn't the vulnerabilities be same if there was no change made to the sbom or the image

@afdesk afdesk added the kind/bug Categorizes issue or PR as related to a bug. label May 10, 2023
@afdesk afdesk self-assigned this May 10, 2023
@knqyf263 knqyf263 added this to the v0.42.0 milestone May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants