Replies: 1 comment
-
|
hello @szigetics We use GitLab advisory database for GitLab contains 3 advisories - https://gitlab.com/gitlab-org/advisories-community/-/tree/main/conan/pcre2?ref_type=heads That is why Trivy doesn't show vulnerabilies. Regards, Dmitriy |
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
Uh oh!
There was an error while loading. Please reload this page.
-
Question
I am trying to detect open CVEs in my conan dependencies using the following approach :
Requirements for running the above :
conan.lock*. Here is an example file (in a zip, which must be extracted before running the script) : conan.zipThe above conan.lock file contains pcre2 version 10.42, which is known for having open CVEs ( see the release hsitory of : https://github.com/PCRE2Project/pcre2/releases ) .
For some reason the trivy sarif result file doesn't contain anything about this : trivy_scan_results.zip
Could you please help me figure out why no CVEs are being reported? Is there something I am doing wrong, or is it Trivy that is not reporting these CVEs correctly? Or is it because I am still using conan1 instead of conan2?
Thank you for your help in advance! 🙏
Target
Filesystem
Scanner
Vulnerability
Output Format
SARIF
Mode
Standalone
Operating System
macOS Sequoia (15.7.1 (24G231))
Version
Beta Was this translation helpful? Give feedback.
All reactions