Replies: 5 comments
-
hi @pealtrufo – looks like this image Currently this is working as expected. If we don't have information about the image we don't fail out the scan. @knqyf263 may have more thoughts on this. |
Beta Was this translation helpful? Give feedback.
-
For example, Debian 7 has reached EOL and security patches will not be released anymore. In this case, Trivy can detect vulnerabilities disclosed before EOL because there are security advisories. Even if it is no longer supported, I think we should detect vulnerabilities as much as possible. But they are not all vulnerabilities for the reason above. Therefore, Trivy displays the warning. |
Beta Was this translation helpful? Give feedback.
-
In my case, I'm building an image based on |
Beta Was this translation helpful? Give feedback.
-
I also stumbled on this strange message when scanning an image based on Debian stable, but with selected packages from bullseye added.
A look at trivy's os detection reveals that the detection is implemented in Trivy's os detector evaluates the returned flags to instantiate the corresponding scanner. trivy/pkg/detector/ospkg/detect.go Line 72 in 5b27862 And here might be the problem: trivy/pkg/detector/ospkg/debian/debian.go Line 21 in 5b27862 trivy/pkg/detector/ospkg/debian/debian.go Line 133 in 5b27862 So the returned message might be bogus. Disclaimer: I'm not fluent in Go. Could somebody please verify my assumptions? |
Beta Was this translation helpful? Give feedback.
-
This issue is stale because it has been labeled with inactivity. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I am scanning image 'openjdk:9-b130-jdk' but I get below output:
Is this the expected behaviour? I am not sure I understand... If it is a no longer supported OS version, shouldn't trivy fail rather than report no vulnerabilities?
I am using trivy version 0.9.2
Thanks
Beta Was this translation helpful? Give feedback.
All reactions