Open mikhailzakhryapin opened 1 year ago
I think what we should do is detect the running kernel version. Welcome any other ideas.
We also need to consider how this works with different targets. Scanning kernel vulnerabilities via image scanning doesn't make alot of sense given that containers are abstracted away from the kernel (and trivy is often run as container itself). Would it make sense to make this a VM target feature? then we can also detect the running kernel with more confidence or have target specific flags (like k8s api-version flag in k8s target)
First, container images don't show the Linux kernel in the list of installed packages. Trivy doesn't detect kernel vulnerabilities anyway.
This issue is mainly relevant to host scanning like trivy rootfs
or trivy vm
. @mikhailzakhryapin Please correct me if I'm wrong.
@knqyf263 That's correct. It relates to scanning host. Sorry that I did not mention it in my first post. We are developing the running kernel detection feature and ready to share the code as soon as we finish it.
Great! Looking forward to seeing it.
@knqyf263 That's correct. It relates to scanning host. Sorry that I did not mention it in my first post. We are developing the running kernel detection feature and ready to share the code as soon as we finish it.
Is there any update on this feature? Definitely interested in it.
Any update?
I'd also be very interested in this as a cloud provider
Hi,
apt upgrade
and upgrade kernel to version 2 that address the vulnerability found in step 1.apt autoremove
, kernel version 1 is removed from the disk and Trivy shows that there is no vulnerability on this hostI would like to have command line option that will hide old version of the kernel appearing in the Trivy report.