-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 False-Positive Secret Detection - Base64String Matches AWS Access Key ID Pattern #2060
Comments
It appears that this is also happening for me, for portions of the default web.config file in windows containers.
|
Thanks @DmitriyLewen, in the Secrets Configuration documentation, I don't see an example of how to skip a specific file or directory. I only see how to disable rules. Can the documentation be updated with an example on how to ignore paths/files? Thanks. |
@AErmie Please see also: We're trying to improve this rule now. Thanks for your patience. |
Thanks @knqyf263, my apologies, what I meant was, I didn't see an example of how to include skipping a specific file or directory using the Thank you for everyone's work on improving the rule. |
I also need an example of ignoring a path from a config file. I want the ignored files to be in source control and not configured on the command line. |
For instance I would expect the following to ignore files under
|
This issue is stale because it has been labeled with inactivity. |
Checklist
-f json
that shows data sources and make sure that the security advisory is correct.Description
Trivy
image
scan identifies a critical secret vulnerability. We believe this is a false positive, as the matched "secret" is actually part of a base64string of a mock image we have in the source code and gets transpired in a backend.js file.We don't want to suppress the secret rule completely (as we want to catch any legitimate ones).
JSON Output of run with
-debug
:Trivy Debug output
Trivy
-f JSON
outputOutput of
trivy -v
:Digest: sha256:5c8043510bb84ed663a4c0b23887c96edb7e78093bceef0083921887e961494f Status: Downloaded newer image for aquasec/trivy:latest docker.io/aquasec/trivy:latest Version: 0.27.1
Additional details (base image name, container registry info...):
I am running Trivy via the Docker container using the following:
The text was updated successfully, but these errors were encountered: