Trivy detects secret in trivy's own cached policies #7970
Replies: 4 comments 1 reply
-
I'm experiencing this while using the GitHub action. My config is as follows. Workflow config:
Output:
|
Beta Was this translation helpful? Give feedback.
-
@nikpivkin I think this is probably due to the new examples being pulled into the bundle as they're yaml and trivy scanning on them. Could you take a look? |
Beta Was this translation helpful? Give feedback.
-
Opened a PR for a fix aquasecurity/trivy-checks#292 |
Beta Was this translation helpful? Give feedback.
-
We've released a new bundle that should fix this https://github.com/aquasecurity/trivy-checks/releases/tag/v1.3.1 |
Beta Was this translation helpful? Give feedback.
-
IDs
aws-access-key-id
Description
I noticed that since Monday afternoon trivy filesystem scans are failing on Rocky 8 and 9 when the [misconfig] built-in checks are updated.
Here is an example of the latest trivy (v0.57.1) failing to download the latest
trivy-checks
update and the scan passing:Here is an example of the
trivy-checks
download succeeding and then a plaintext secret is detected in trivy's own cached policies:This is not being deployed in AWS and there is no AWS_ACCESS_KEY_ID variable present in the environment variables or in any other files.
I am seeing this issue with Rocky 8.10 and 9.4. I did not have this issue until about 2 days ago. I thought it might be related to the v0.57.1 release, which included some AWS updates, but v0.57.0 does the same thing.
Reproduction Steps
Target
Filesystem
Scanner
Secret
Target OS
Rocky 8.10 and Rocky 9.4
Debug Output
Version
Checklist
-f json
that shows data sources and confirmed that the security advisory in data sources was correctBeta Was this translation helpful? Give feedback.
All reactions