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.7-slim to 3.13.0b1-slim #169

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

Conversation

ekmixon
Copy link
Owner

@ekmixon ekmixon commented May 9, 2024

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

  • src/recommendationservice/Dockerfile

We recommend upgrading to python:3.13.0b1-slim, as this image has only 50 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 829 Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-5927132
Mature
high severity 829 Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-5927132
Mature
high severity 721 Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-6210098
Proof of Concept
high severity 721 Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-6210098
Proof of Concept
high severity 614 CVE-2023-5363
SNYK-DEBIAN12-OPENSSL-6032384
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:

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

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

Copy link

guardrails bot commented May 9, 2024

⚠️ We detected 1 security issue in this pull request:

Insecure Access Control (1)
Severity Details Docs
High Title: Missing User Instruction
📚

More info on how to fix Insecure Access Control in Dockerfile.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

Micro-Learning Topic: Insufficient access control (Detected by phrase)

Matched on "Insecure Access Control"

Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users' accounts, view sensitive files, modify other users’ data, change access rights, etc. Source: https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project

Try a challenge in Secure Code Warrior

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants