Open flo-mic opened 3 months ago
Hello,
Do you have more details ? Were those vulnerabilities reported in the base image(s) with a static scanning tool ?
If so, the vast majority of the time, those vulnerabilities are pretty much meaningless (because they are in packages present in the base image, but nothing makes use of them), but if you do find a vulnerability in something that is actively used in the image, please let us know.
A possible workaround if your security team insists on having "clean" images would be to build your own image based on our own and run apk update
/apt upgrade
/... or just rebuild the image using our Dockerfile.
Also crowdstrice
?
here an example using trivy
an open source scanner
trivy image crowdsecurity/openresty
Scan using a locally built image using repo and no modifications:
Seems the upstream alpine image provided by openresty
still has some unresolved patches
Hi Crowdsec Team, first of all thanks for this great product, I used it a lot in the past months and really liked it.
Unfortunately this image as well as the kubernetes lapi and deamonsets expose a lot of vulnerabilities, so I was forced to remove this from our production environments. Is there any process in place to watch and remediate vulnerabilities? As this is loaded in the ingress controller and therefore public phasing, our security team was forcing the shutdown of this security solution due to security issues. Actually most of our production vulnerabilities was caused by crowdstrice in the last weeks :(