Closed rwjack closed 2 hours ago
Hello,
None of those vulnerabilities impact this tool because this is related to unused dependencies.
hey @ldez, I'm not familiar with go, but I think I see what you're saying.
On the other hand, Traefik doesn't seem to be an unused "indirect" dependency, and all of the above findings have been fixed in 2.11.9
, which is already in master - which brings us to my initial question, can you make a workflow that automatically creates new releases with bumped dependencies?
Even if there are no new features, recreating the image with a fresh base OS image, and updated dependencies in this case, resolves most vulnerabilities over time.
There are no vulnerabilities to resolve because there are no vulnerabilities.
Your tools is just reporting false positives.
What do you mean there are no vulnerabilities to resolve? My "tool" scanned your latest image and found all the above vulnerabilities:
The image is almost a year old.
You are pushing directly to master on the repo here, but you are not making a new release, hence vulnerabilities exist in the "latest" release.
As for the "master image" workflow, I'm telling you that if you push a new release often, the image will get recreated and most future/potential base OS package vulnerabilities will be taken care of.
You have found nothing.
You just run a vulnerability tool that reports false positives.
traefik-certs-dumper is not impacted by those vulnerabilities.
Hey, the latest released version has quite a few vulnerabilities:
I suppose half of these are fixed in the master version, but there is no docker image of it.
Would you be willing to make a workflow that publishes a master (nightly) image, alongside tagged releases?