-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Different vulnerability lists after upgrade to 0.20.0 #1815
Comments
@DmitriyLewen Can you look into it? |
Hello @ajw3-msw Regards, Dmitriy |
Hello @ajw3-msw
Trivy found all vulnerabilities, but the vulnerabilities are of different severity (e.g. Regards, Dmirtiy |
Hi Dmitriy. Thanks for investigating promptly for me - I understand your explanation. I'll close the ticket. Best regards. |
@DmitriyLewen Cool! Thanks for investigating! |
Description
Running a vulnerability scan against the same image on Trivy v0.19.2 and v0.20.0 produces a list of different CVEs
What did you expect to happen?
The list of CVEs should be the same (or at least, the new Trivy version list should contain a superset of the previous CVEs) when run against the same image.
What happened instead?
The list of CVEs was different.
Output of run with
-debug
:The output is quite verbose. I'll attach the two separate outputs as "trivy0.20.0.txt" and "trivy0.19.2.txt".
trivy0.19.2.txt
trivy0.20.0.txt
An example of a CVE that goes "missing" in 0.20.0 is CVE-2005-2541.
An example of a CVE that "appears" in 0.20.0 is CVE-2019-3881.
Output of
trivy -v
:Commands run were:
and
Could you advise?
The text was updated successfully, but these errors were encountered: