Skip to content
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

[Snyk] Security upgrade python from 3.10.7-alpine to 3.14.0a1-alpine #10

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

Conversation

gitafolabi
Copy link
Owner

snyk-top-banner

Snyk has created this PR to fix 5 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):

  • dbt/Dockerfile

We recommend upgrading to python:3.14.0a1-alpine, as this image has only 0 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 Double Free
SNYK-ALPINE316-OPENSSL-3314624
  614  
high severity Access of Resource Using Incompatible Type ('Type Confusion')
SNYK-ALPINE316-OPENSSL-3314641
  614  
high severity Use After Free
SNYK-ALPINE316-OPENSSL-3314643
  614  
high severity Improper Certificate Validation
SNYK-ALPINE316-OPENSSL-3368756
  614  
high severity Out-of-Bounds
SNYK-ALPINE316-SQLITE-6179509
  614  

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:

🦉 Double Free
🦉 Access of Resource Using Incompatible Type ('Type Confusion')
🦉 Use After Free

Copy link

DryRun Security Summary

The provided code change updates the Dockerfile for a dbt (Data Build Tool) project, including upgrading the base Docker image to a newer, albeit alpha, version of Python, using a multi-stage build approach, and installing the dbt project and its dependencies.

Expand for full summary

Summary:

The provided code change is an update to the Dockerfile used for the dbt (Data Build Tool) project. The key changes include upgrading the base Docker image from python:3.10.7-alpine to python:3.14.0a1-alpine, which indicates a move to a newer, albeit alpha, version of Python. This version upgrade can introduce potential security implications and should be thoroughly tested to ensure compatibility and identify any new vulnerabilities. Additionally, the Dockerfile is using a multi-stage build approach, which is a common practice for creating optimized Docker images and can help reduce the attack surface of the final Docker image. Finally, the Dockerfile is installing the dbt project and its dependencies, which should be kept up-to-date and free of known vulnerabilities.

Files Changed:

  • dbt/Dockerfile: The Dockerfile has been updated with the following changes:
    1. The base Docker image has been upgraded from python:3.10.7-alpine to python:3.14.0a1-alpine, indicating a move to a newer, alpha version of Python. This change should be thoroughly tested to ensure compatibility and identify any new vulnerabilities.
    2. The Dockerfile is using a multi-stage build approach, which can help reduce the attack surface of the final Docker image by minimizing the number of installed packages and dependencies.
    3. The Dockerfile is installing the dbt (Data Build Tool) project and its dependencies. It is important to ensure that the project and its dependencies are kept up-to-date and free of known vulnerabilities.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer Findings
Sensitive Files Analyzer 1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

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