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.8-slim to 3.13.0a4-slim #6

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

Conversation

subhayu99
Copy link
Member

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

  • Dockerfile-for-Website

We recommend upgrading to python:3.13.0a4-slim, as this image has only 45 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
high severity 400 Resource Exhaustion
SNYK-DEBIAN12-EXPAT-6227597
No Known Exploit
medium severity 300 Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
SNYK-DEBIAN12-EXPAT-6227603
No Known Exploit
high severity 471 Allocation of Resources Without Limits or Throttling
SNYK-DEBIAN12-SYSTEMD-6277507
No Known Exploit
high severity 471 Allocation of Resources Without Limits or Throttling
SNYK-DEBIAN12-SYSTEMD-6277507
No Known Exploit
critical severity 500 Integer Overflow or Wraparound
SNYK-DEBIAN12-ZLIB-6008963
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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Resource Exhaustion

Copy link

github-actions bot commented Mar 1, 2024

Terraform Format and Style 🖌``

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Terraform Plan 📖failure

Show Plan

terraform
Running plan in Terraform Cloud. 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-gWDKXBUWAzxWEmjY

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: 0de93517-0b01-4fad-bda7-2118b95ad379
│
│   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