[Snyk] Security upgrade python from 3.11.7 to 3.14.0a3

[gitworkflows]

User description

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):

• docker/Dockerfile

We recommend upgrading to python:3.14.0a3, as this image has only 181 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
	Integer Overflow or Wraparound SNYK-DEBIAN12-AOM-7197979	714
	Link Following SNYK-DEBIAN12-GIT-6846203	714
	CVE-2024-37371 SNYK-DEBIAN12-KRB5-7411315	714
	CVE-2024-37371 SNYK-DEBIAN12-KRB5-7411315	714
	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.

---

PR Type

Enhancement

---

Description

• Upgraded Python base image in Dockerfile from version 3.11.7 to 3.14.0a3 to address multiple security vulnerabilities:
  • Integer Overflow vulnerability in AOM package
  • Link Following vulnerability in Git package
  • Multiple vulnerabilities in KRB5 package
• The new image version has significantly fewer known vulnerabilities (181)
• Update affects the backend build stage of the multi-stage Dockerfile

---

Changes walkthrough 📝

	Relevant files
Dependencies	Dockerfile Python Base Image Version Upgrade for Security                      docker/Dockerfile Upgraded Python base image from version 3.11.7 to 3.14.0a3 to address security vulnerabilities +1/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request upgrades the Python base image used in the Dockerfile from 3.11.7 to 3.14.0a3 to address three critical vulnerabilities.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Upgrade the Python base image to patch vulnerabilities.	Changed the base image version in the Dockerfile from python:3.11.7 to python:3.14.0a3 to mitigate Integer Overflow or Wraparound (SNYK-DEBIAN12-AOM-7197979), Link Following (SNYK-DEBIAN12-GIT-6846203), and CVE-2024-37371 (SNYK-DEBIAN12-KRB5-7411315) vulnerabilities.	docker/Dockerfile

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

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.

[gitworkflows]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Version Stability Python 3.14.0a3 is an alpha release and may have stability issues in production. Consider using a stable production release instead.

[deepsource-io]

Here's the code health analysis summary for commits d7f231f..2d96b12. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Using alpha/pre-release versions in production environments can lead to stability and security issues Avoid using alpha/pre-release Python versions (3.14.0a3) in production environments as they may contain unstable features and security vulnerabilities. Use the latest stable Python version instead. docker/Dockerfile [16] -FROM python:3.14.0a3 AS backend-build +FROM python:3.11.8 AS backend-build Apply this suggestion Suggestion importance[1-10]: 10 Why: Using an alpha version (3.14.0a3) in a production Dockerfile is a critical security and stability risk. The suggestion to use a stable version (3.11.8) is crucial for maintaining a secure and reliable production environment.	10

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

Action: backend-tests

Failed stage: Startup script launch (Slow) [❌]

Failure summary: The action failed due to Node.js version incompatibility: The installed Node.js version (v20.13.1) is not compatible with the required version (^20.17.0 || >=22.9.0) NPM version 11.0.0 installation failed because it requires a newer Node.js version The build process failed during npm install npm@latest command due to this version mismatch

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1819: #12 0.841 npm ERR! code EBADENGINE 1820: #12 0.843 npm ERR! engine Unsupported engine 1821: #12 0.844 npm ERR! engine Not compatible with your version of node/npm: [email protected] 1822: #12 0.845 npm ERR! notsup Not compatible with your version of node/npm: [email protected] 1823: #12 0.846 npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"} 1824: #12 0.846 npm ERR! notsup Actual: {"npm":"10.5.2","node":"v20.13.1"} 1825: #12 0.848 1826: #12 0.848 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-12-20T06_39_13_835Z-debug-0.log 1827: #12 ERROR: process "/bin/sh -c npm install npm@latest --location=global && npm install && PUBLIC_URL=/static/reactapp/ npm run build" did not complete successfully: exit code: 1 1828: failed to solve: process "/bin/sh -c npm install npm@latest --location=global && npm install && PUBLIC_URL=/static/reactapp/ npm run build" did not complete successfully: exit code: 1 ... 1832: 0.843 npm ERR! engine Unsupported engine 1833: 0.844 npm ERR! engine Not compatible with your version of node/npm: [email protected] 1834: 0.845 npm ERR! notsup Not compatible with your version of node/npm: [email protected] 1835: 0.846 npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"} 1836: 0.846 npm ERR! notsup Actual: {"npm":"10.5.2","node":"v20.13.1"} 1837: 0.848 1838: 0.848 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-12-20T06_39_13_835Z-debug-0.log 1839: ------ 1840: ##[error]Process completed with exit code 17. 1841: ##[group]Run docker ps -a 1842: �[36;1mdocker ps -a�[0m 1843: �[36;1mdocker logs threatmatrix_uwsgi�[0m 1844: �[36;1mdocker logs threatmatrix_daphne�[0m 1845: shell: /usr/bin/bash -e {0} 1846: ##[endgroup] 1847: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1848: Error response from daemon: No such container: threatmatrix_uwsgi 1849: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.