Replies: 1 comment
-
@pogepoge9 thanks for the report! i'll take a look at this issue |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
I tried scanning the Kubernetes control plane and node components for vulnerabilities, but none were detected.
From my debugging, it seems to be due to the
scanOptions
variable in thescanK8sVulns
function not setting the default value forPkgRelationships
.So it seems that all Packages are set to [] in the
filterPkgByRelationship
function, which matches this if statement and skips the scanning process.I was able to successfully scan for vulnerabilities after initializing
scanOptions
by adding the followingPkgRelationships
values, like so:Is this the intended behavior (by design), or is it a bug?
My test environment details are below:
Desired Behavior
Actual Behavior
Reproduction Steps
Target
Kubernetes
Scanner
Vulnerability
Output Format
Table
Mode
Standalone
Debug Output
Operating System
macOS Sonoma 14.5
Version
Checklist
trivy clean --all
Beta Was this translation helpful? Give feedback.
All reactions