We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The latest testrail images have a lot of CRITICAL CVEs.
How to scan: docker run --rm -v /var/run/docker.sock:/var/run/docker.sock aquasec/trivy:0.21.0 -d image --severity CRITICAL testrail/php:6.3.1
docker run --rm -v /var/run/docker.sock:/var/run/docker.sock aquasec/trivy:0.21.0 -d image --severity CRITICAL testrail/php:6.3.1
One of the possible solutions is to switch base image from php:7.2-fpm to alpine based (e.g. php:7.4-fpm-alpine3.14)
The text was updated successfully, but these errors were encountered:
The latest docker image: testrail/apache:7.0.2 Also has a lot of CRITICAL CVEs:
docker run --rm -v /var/run/docker.sock:/var/run/docker.sock aquasec/trivy:0.21.0 -d image --severity CRITICAL testrail/apache:7.0.2
Sorry, something went wrong.
No branches or pull requests
The latest testrail images have a lot of CRITICAL CVEs.
How to scan:
docker run --rm -v /var/run/docker.sock:/var/run/docker.sock aquasec/trivy:0.21.0 -d image --severity CRITICAL testrail/php:6.3.1
One of the possible solutions is to switch base image from php:7.2-fpm to alpine based (e.g. php:7.4-fpm-alpine3.14)
The text was updated successfully, but these errors were encountered: