Skip to content
Discussion options

You must be logged in to vote

Hi @av-commits, thanks for the detailed report!

This is a known limitation rather than a false positive we can fix on the detection side.

To build the list of Go dependencies, Trivy relies on the module information embedded in the binary (the same data as go version -m). That output contains only modules, not the individual sub-packages that were imported. Because of this, Trivy cannot tell whether the vulnerable golang.org/x/crypto/openpgp sub-package is actually used, and it flags the whole module as affected.

Extracting the list of imported sub-packages from a binary is possible in theory, but it's problematic in practice and comes with a number of caveats, so we don't do it today.

We …

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@av-commits
Comment options

@DmitriyLewen
Comment options

@av-commits
Comment options

Answer selected by av-commits
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
scan/vulnerability Issues relating to vulnerability scanning target/container-image Issues relating to container image scanning
2 participants