-
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
Trivy not detecting CVE-2021-43798: Grafana directory traversal ? #1459
Comments
I can confirm that this container version is vulnerable:
|
@knqyf263 I suspect Grafana is not installed through a package manager, but it's deployed as a binary, which currently Trivy does not support? |
@stefanlasiewski thanks for your report! |
@jerbia you're right, Grafana deployed as a binary, and |
@afdesk Interesting. Is there a way for Trivy to detect this? Does Trivy look at the md5 sums of installed binaries, for example? For the record,
And neither does Anchore's SBOM method with
|
@stefanlasiewski in this case, maybe i miss something Thanks for your investigation! |
This issue is stale because it has been labeled with inactivity. |
Hi @afdesk Do you happen to have any fixes in mind for this? It's till happening on Trivy 0.23.
|
This issue is stale because it has been labeled with inactivity. |
Description
Grafana issued a notice about CVE-2021-43798: Grafana directory traversal this week. It affects all Grafana 8.x instances.
https://grafana.com/blog/2021/12/08/an-update-on-0day-cve-2021-43798-grafana-directory-traversal/
However, Trivy doesn't seem to be picking it up. Why os this?
What did you expect to happen?
I expect this command to list CVE-2021-43798:
What happened instead?
It doesn't list this CVE:
Output of run with
-debug
:Output of
trivy -v
:Additional details (base image name, container registry info...):
n/a
The text was updated successfully, but these errors were encountered: