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.9-slim to 3.14.0a1-slim #28

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

Conversation

subhayu99
Copy link
Member

snyk-top-banner

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

  • Dockerfile-for-API

We recommend upgrading to python:3.14.0a1-slim, as this image has only 35 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
critical severity Integer Overflow or Wraparound
SNYK-DEBIAN12-ZLIB-6008963
  500  
medium severity Improper Authentication
SNYK-DEBIAN12-PAM-8352887
  471  
medium severity Improper Authentication
SNYK-DEBIAN12-PAM-8352887
  471  
medium severity Improper Authentication
SNYK-DEBIAN12-PAM-8352887
  471  
medium severity Improper Authentication
SNYK-DEBIAN12-PAM-8352887
  471  

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:

🦉 Improper Authentication

Copy link

Terraform Format and Style 🖌``

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Terraform Plan 📖failure

Show Plan

terraform
Running plan in HCP Terraform. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

To view this run in a browser, visit:
https://app.terraform.io/app/example-org-bae840/resume-builder/runs/run-aA7pXzByNxYyAuJf

Waiting for the plan to start...

Terraform v1.1.6
on linux_amd64
Initializing plugins and modules...
tls_private_key.terraform-key: Refreshing state... [id=b01bdea57b18f807534aebc5479a1d8154d78703]
╷
│ Error: error configuring Terraform AWS Provider: error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid.
│ 	status code: 403, request id: c2ab5236-ed31-4454-9538-8c99fa1e52a1
│
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on main.tf line 19, in provider "aws":
│   19: provider "aws" {
│
╵
Operation failed: failed running terraform plan (exit 1)

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.

Pusher: @subhayu99, Action: pull_request

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