[Snyk] Security upgrade python from 3.6-slim to 3.13.0b1-slim

[mikolajroszak]

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

• docker/Dockerfile.python-2

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
	714	Use After Free SNYK-DEBIAN11-GLIBC-1296898	No Known Exploit
	714	Buffer Overflow SNYK-DEBIAN11-GLIBC-2340908	No Known Exploit
	714	Buffer Overflow SNYK-DEBIAN11-GLIBC-2340922	No Known Exploit
	829	Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133	Mature
	829	Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133	Mature

---

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:

🦉 Use After Free

[cloudflare-workers-and-pages]

Deploying snyk-1 with    Cloudflare Pages

Latest commit:	c95c2dc
Status:	🚫  Build failed.

View logs

[secure-code-warrior-for-github]

Micro-Learning Topic: Buffer overflow (Detected by phrase)

Matched on "Buffer Overflow"

What is this? (2min video)

A buffer overflow condition exists when a program attempts to put more data in a buffer than it can hold or when a program attempts to put data in a memory area past a buffer.

Try a challenge in Secure Code Warrior

Micro-Learning Topic: Use-after-free (Detected by phrase)

Matched on "Use After Free"

What is this? (2min video)

Dereferencing pointers to objects that have already been freed opens the door to execution of arbitrary code. Attackers may be able to insert instructions at the freed memory location in order to trigger the exploit when the pointer is used after the memory has been freed.

Try a challenge in Secure Code Warrior