[Snyk] Security upgrade alpine from latest to 3.17.3 #1
Conversation
2022-06-30 23:02:1656601363
Update README_CN.md
Merge pull request GhostTroops#67 from hktalent/main
Merge pull request GhostTroops#68 from hktalent/dev
Merge pull request GhostTroops#69 from hktalent/main
…vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-ALPINE317-OPENSSL-3368755 - https://snyk.io/vuln/SNYK-ALPINE317-OPENSSL-3368755 - https://snyk.io/vuln/SNYK-ALPINE317-OPENSSL-5291795 - https://snyk.io/vuln/SNYK-ALPINE317-OPENSSL-5291795
|
SonarCloud Quality Gate failed.
|
|
You have successfully added a new SonarCloud configuration ``. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab. |
![prisma-cloud-devsecops[bot]](https://avatars.githubusercontent.com/in/135857?s=60&v=4){kind=small}
| @@ -1,6 +1,6 @@ | |||
| FROM golang:1.18.3-alpine AS build-env | |||
There was a problem hiding this comment.
Healthcheck instructions have not been added to container images
Resource: /vendor/github.com/projectdiscovery/mapcidr/Dockerfile. | Bridgecrew ID: BC_DKR_2 | Checkov ID: CKV_DOCKER_2
Description
We recommend that you add the HEALTHCHECK instruction to your Docker container images to ensure that health checks are executed against running containers.An important security control is that of availability. Adding the HEALTHCHECK instruction to your container image ensures that the Docker engine periodically checks the running container instances against that instruction to ensure that containers are still operational.
Based on the results of the health check, the Docker engine could terminate containers which are not responding correctly, and instantiate new ones.
Benchmarks
- CIS DOCKER V1.2 4.6
| @@ -1,6 +1,6 @@ | |||
| FROM golang:1.18.3-alpine AS build-env | |||
There was a problem hiding this comment.
A user for the container has not been created
Resource: /vendor/github.com/projectdiscovery/mapcidr/Dockerfile. | Bridgecrew ID: BC_DKR_3 | Checkov ID: CKV_DOCKER_3
Description
Containers should run as a non-root user. It is good practice to run the container as a non-root user, where possible. This can be done either via the ```USER``` directive in the ```Dockerfile``` or through ```gosu``` or similar where used as part of the ```CMD``` or ```ENTRYPOINT``` directives.Benchmarks
- CIS DOCKER V1.2 4.1
This PR was automatically created by Snyk using the credentials of a real user.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR
We recommend upgrading to
alpine:3.17.3, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.Some of the most important vulnerabilities in your base image include:
SNYK-ALPINE317-OPENSSL-3368755
SNYK-ALPINE317-OPENSSL-3368755
SNYK-ALPINE317-OPENSSL-5291795
SNYK-ALPINE317-OPENSSL-5291795
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.