[Snyk] Security upgrade nginx from latest to 1.21#53
Open
snyk-bot wants to merge 1 commit into
Open
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-DEBIAN11-GZIP-2444256 - https://snyk.io/vuln/SNYK-DEBIAN11-LIBXML2-2806812 - https://snyk.io/vuln/SNYK-DEBIAN11-OPENLDAP-2808413 - https://snyk.io/vuln/SNYK-DEBIAN11-OPENSSL-2807596 - https://snyk.io/vuln/SNYK-DEBIAN11-OPENSSL-2807596
![bridgecrew[bot]](https://avatars.githubusercontent.com/in/52968?s=60&v=4){kind=small}
| @@ -1,6 +1,6 @@ | |||
| # NGINX image with build artifact | |||
There was a problem hiding this comment.
Ensure healthcheck instructions have been added to container images
Resource: /proxy/Dockerfile. | ID: BC_DKR_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 @@ | |||
| # NGINX image with build artifact | |||
There was a problem hiding this comment.
Ensure a user for the container has been created
Resource: /proxy/Dockerfile. | ID: BC_DKR_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 file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
nginx:1.21, as this image has only 86 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-DEBIAN11-GZIP-2444256
SNYK-DEBIAN11-LIBXML2-2806812
SNYK-DEBIAN11-OPENLDAP-2808413
SNYK-DEBIAN11-OPENSSL-2807596
SNYK-DEBIAN11-OPENSSL-2807596
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.