8000 [Snyk] Security upgrade python from 3.7-slim to 3.13.3-slim by toharzand · Pull Request #88 · toharzand/terragoat · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Snyk] Security upgrade python from 3.7-slim to 3.13.3-slim #88

New issue

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

toharzand
Copy link
Owner

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

  • terraform/aws/resources/Dockerfile

We recommend upgrading to python:3.13.3-slim, as this image has only 38 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-5927132
  829  
high severity Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-5927132
  829  
high severity Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-6210098
  721  
high severity Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-6210098
  721  
critical severity CVE-2024-37371
SNYK-DEBIAN12-KRB5-7411315
  714  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
1 Security Hotspot

See analysis details on SonarQube Cloud

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 +1 @@
FROM python:3.7-slim
FROM python:3.13.3-slim

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: /terraform/aws/resources/Dockerfile. | Checkov ID: CKV_DOCKER_3

Description

The policy's primary purpose is to verify that a dedicated user has been explicitly created for running the container. This is essential to avoid running the container with root privileges, which could introduce significant security risks in case of a compromise. Running containers as a non-root user reduces the potential impact of a security breach.

@@ -2,0 +1 @@
FROM python:3.13.3-slim

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: /terraform/aws/resources/Dockerfile. | Checkov ID: CKV_DOCKER_2

Description

This rule detects whether HEALTHCHECK instructions have been added to Docker container images. These instructions provide a way to check the health of the running container, ensuring that issues are detected and handled promptly, improving the reliability and stability of your containerized applications. Adding HEALTHCHECK instructions to your Dockerfiles follows best practices for Docker container health management.

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.

2 participants
0