Trivy randomly fail to find vulnerabilities and reports 0 issues #7758
krab-skunk
started this conversation in
Bugs
Replies: 2 comments 25 replies
-
|
That's interesting @krab-skunk - I've run Trivy in a loop for 30min or so but haven't seen this behavior yet. Where are you running Trivy? |
Beta Was this translation helpful? Give feedback.
24 replies
-
|
Hello @krab-skunk 1 small question - do you have statistic for issues by OSes? As i was worried - problem in logic for work with trivy-db. Can you replace ➜ go mod edit -replace github.com/aquasecurity/trivy-db=github.com/DmitriyLewen/trivy-db@1f947cbbdd441fe978eb812ed6ded10d1762cddb
➜ go mod tidy |
Beta Was this translation helpful? Give feedback.
-
|
@DmitriyLewen first of all, no apologies please as its already awesome you guys wanna help us out on this bug ;)
No, we don't yet keep of this kind of historical data per images, i could check what we can do about it but that would surely require us quite some time in order to reproduce this scenario.
Its maybe too early, but i have a feeling that its occurring way more when i allow more than 1 trivy process to run per pods ( i usually allow 2 to 3), i switched to force only 1 trivy process per pod and the issue didn't occurred this week, hazard, i dunno, too early to say i guess Btw, thanks again for your help ;) |
Beta Was this translation helpful? Give feedback.
-
|
i'll continue from my pro account in order to get notification at work ;) |
Beta Was this translation helpful? Give feedback.
-
Then you don't need to do that. It's better to focus on checking with new logs.
I thought it might be related to multiple simultaneous DB queries. But bbolt should handle that correctly... |
Beta Was this translation helpful? Give feedback.
-
|
Here are the logs for Let me know if that extract of logs is what you needed, thanks ;) Worth adding, trivy didn't failed for almost a week with only 1 process, the very same night (yesterday) i change settings to allow 2 process per pod, i have plenty of failed scans |
Beta Was this translation helpful? Give feedback.
-
|
I'm seeing the same thing -- nearly identical packages, vulnerabilities are detected in one while the other succeeds with none. We run trivy automatically in a background service, but it's low-throughput so I don't believe we've done any simultaneous scans. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Hello @bloomadcariad Do you see vulns for |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
We run a Trivy scanning job on an AWS EC2, and sometimes it will find every issues for all images, and few hours later, for the very same scan with the same images, it will simply find 0 vulnerabilities for all of the images, while the previous scan found 13000+ CVEs
Here are an example log: example of scanning
bitnami/redis-exporter:1.43.0-debian-11-r4and report 0 issuesThe worst part here is that it fail silently, it doesn't say anywhere cannot scan or anything, it look like a perfectly legit scan, just found 0 CVEs
30min later, scanning the very same
bitnami/redis-exporter:1.43.0-debian-11-r4image will report 308 CVEsAnd few hours later, it will again report 0 CVEs found
The only difference i see between those 2 scans, is that the one that found some issues had this new line
Are there some quotas of vulnerabilities found from the same IP address ?? What could explain this discrepancy ?
Thanks a lot
Desired Behavior
Not having discrepancies
Actual Behavior
Mentioned in the description
Reproduction Steps
Mentioned in the descriptionTarget
None
Scanner
None
Output Format
None
Mode
None
Debug Output
Mentioned in the descriptionOperating System
python:3.11.8-alpine3.19
Version
Checklist
trivy clean --allBeta Was this translation helpful? Give feedback.
All reactions