-
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
wrong version compare? #1456
Comments
to test, use this commit id: 914096f3e97090bb0dd0106b2d8e8c85cf33448a, i then solved my issues in other ways, but this bug is still there if trivy compares pseudo-versions with versions |
Hi @fragolinux! thanks for your report! |
@fragolinux sorry for waiting. more details about |
but as that second link says, "Pseudo-versions may refer to revisions for which no semantic version tags are available"... so, actually comparing semver tags AND pseudo-versions ones IS wrong, they CAN'T be compared... this is the problem... |
No, it says "no semantic version tags are available". If there is no tag, Go generates pseudo-semantic versions. |
ok, understood, but what to do with images i've no control on, but i need them deployed on my cluster, having trivy blocking them because it compares versions this strange way? Don't want to disable trivy checks, but this is halting PATCHED and NEWER images from being deployed |
This issue is stale because it has been labeled with inactivity. |
Description
testing trivy v0.21.2 on a custom build of the "img" tool, it reports a vulnerability in docker cli library:
github.com/docker/cli | CVE-2021-41092 | HIGH | v0.0.0-20211117234946-dea9396e1842 | v20.10.9 | docker: cli leaks private registry
but that v0.0.0-20211117234946-dea9396e1842 is actually the pseudo-version format of the v20.10.11 library (had to put that in this format because otherwise it does not compile, i'm no "go" expert to fix this), so NEWER than v20.10.9 version that trivy says fixed the issue...
What did you expect to happen?
all vulnerability fixed
What happened instead?
still a vulnerability active, even if on a newer version than the one which fixes the issue reported
Output of run with
-debug
:Output of
trivy -v
:Additional details (base image name, container registry info...):
pushed my mods in this feature branch: https://github.com/EcoMind/img/tree/feature/CVE-2021-41092
just clone it, go in its folder and run
docker build -t CVE-2021-41092 .
then
trivy image CVE-2021-41092
The text was updated successfully, but these errors were encountered: