Skip to content

Conversation

@ddzzj
Copy link
Owner

@ddzzj ddzzj commented Dec 8, 2023

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

  • images/runtimes/go1.16/Dockerfile.x86_64

We recommend upgrading to golang:1.20.11, as this image has only 74 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:

Severity Priority Score / 1000 Issue Exploit Maturity
critical severity 271 Integer Overflow or Wraparound
SNYK-DEBIAN11-APR-3261105
No Known Exploit
high severity 561 Resource Exhaustion
SNYK-DEBIAN11-NGHTTP2-5953384
Mature
critical severity 277 Unquoted Search Path or Element
SNYK-DEBIAN11-OPENSSH-5788321
No Known Exploit
critical severity 274 OS Command Injection
SNYK-DEBIAN11-OPENSSL-2933518
No Known Exploit
critical severity 274 OS Command Injection
SNYK-DEBIAN11-OPENSSL-2933518
No Known Exploit

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:

🦉 Resource Exhaustion

Copy link

@prisma-cloud-devsecops prisma-cloud-devsecops bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prisma Cloud has found errors in this PR ⬇️

@@ -1,4 +1,4 @@
FROM golang:1.16
FROM golang:1.20.11

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOW  Healthcheck instructions have not been added to container images
    Resource: /images/runtimes/go1.16/Dockerfile.x86_64. | 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.

@@ -1,4 +1,4 @@
FROM golang:1.16
FROM golang:1.20.11

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOW  A user for the container has not been created
    Resource: /images/runtimes/go1.16/Dockerfile.x86_64. | 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants