[Snyk] Security upgrade python from 3.8 to 3.14.0a2

[ekmixon]

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

• src/loadgenerator/Dockerfile

We recommend upgrading to python:3.14.0a2, as this image has only 180 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
	Inefficient Regular Expression Complexity SNYK-DEBIAN12-PYTHON311-7886332	614
	Inefficient Regular Expression Complexity SNYK-DEBIAN12-PYTHON311-7886332	614
	Inefficient Regular Expression Complexity SNYK-DEBIAN12-PYTHON311-7886332	614
	Out-of-Bounds SNYK-DEBIAN12-SQLITE3-6139924	614
	Out-of-Bounds SNYK-DEBIAN12-SQLITE3-6139924	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:

🦉 Inefficient Regular Expression Complexity

Summary by Sourcery

Build:

• Upgrade the base Python image in the Dockerfile from version 3.8 to 3.14.0a2 to address security vulnerabilities.

[sourcery-ai]

Reviewer's Guide by Sourcery

This security-focused PR upgrades the Python base image in the loadgenerator Dockerfile from version 3.8 to 3.14.0a2 to address multiple high-severity vulnerabilities, including issues related to regular expression complexity and out-of-bounds operations.

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

File-Level Changes

Change	Details	Files
Update Python base image version to address security vulnerabilities	Upgrade Python version from 3.8 to 3.14.0a2 Fix high-severity regular expression complexity vulnerabilities Address high-severity out-of-bounds vulnerabilities in SQLite3	src/loadgenerator/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.

[secure-code-warrior-for-github]

Micro-Learning Topic: Inefficient regular expression (Detected by phrase)

Matched on "Inefficient Regular Expression"

What is this? (2min video)

A regular expression that requires exponential time to match certain inputs can be a performance bottleneck, and may be vulnerable to denial-of-service attacks.

Try a challenge in Secure Code Warrior

Micro-Learning Topic: SQL injection (Detected by phrase)

Matched on "SQLI"

What is this? (2min video)

This is probably one of the two most exploited vulnerabilities in web applications and has led to a number of high profile company breaches. It occurs when an application fails to sanitize or validate input before using it to dynamically construct a statement. An attacker that exploits this vulnerability will be able to gain access to the underlying database and view or modify data without permission.

Try a challenge in Secure Code Warrior

Helpful references

• PHP SQL Injection Page - A detailed page on SQL injection in the online PHP manual.
• OWASP SQL Injection Prevention Cheat Sheet - This article is focused on providing clear, simple, actionable guidance for preventing SQL Injection flaws in your applications.
• OWASP SQL Injection - OWASP community page with comprehensive information about SQL injection, and links to various OWASP resources to help detect or prevent it.
• OWASP Query Parameterization Cheat Sheet - A derivative work of the OWASP SQL Injection Prevention Cheat Sheet focused on SQL query parameterization.
• Preventing SQL Injection Attacks With Python - A tutorial on crafting parameterized queries, SQL composition and safe query execution in Python.

[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.

[guardrails]

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

Insecure Access Control (1)

Severity	Details	Docs
High	Title: Missing User Instruction cloud-ops-sandbox/src/loadgenerator/Dockerfile Line 17 in 51484b0 FROM python:3.14.0a2	📚

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

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[secure-code-warrior-for-github]

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