[Snyk] Security upgrade python from 3.8.12-buster to 3.9.12-buster

[ChristianPerez34]

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

We recommend upgrading to python:3.9.12-buster, as this image has only 445 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
	571	Out-of-bounds Write SNYK-DEBIAN10-LIBDE265-2445048	No Known Exploit
	614	Use After Free SNYK-DEBIAN10-LIBXML2-2413976	No Known Exploit
	514	CVE-2021-4160 SNYK-DEBIAN10-OPENSSL-2388381	No Known Exploit
	614	Loop with Unreachable Exit Condition ('Infinite Loop') SNYK-DEBIAN10-OPENSSL-2426310	No Known Exploit
	483	CVE-2022-1271 SNYK-DEBIAN10-XZUTILS-2444279	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.

[semgrep-app[bot]]

Semgrep found 1 dockerfile-source-not-pinned finding:

• Dockerfile: L1

To ensure reproducible builds, pin Dockerfile FROM commands to a specific hash. You can find the hash by running docker pull python and then specify it with python:3.9.12-buster@sha256:<hash goes here>

_{⚪️ This finding does not block your pull request.
🙈 From dockerfile.audit.dockerfile-source-not-pinned.dockerfile-source-not-pinned.}