[Snyk] Security upgrade alpine from 3.14.2 to 3.17

[ekmixon]

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix 5 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):

• Dockerfile

We recommend upgrading to alpine:3.17, as this image has only 0 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
	Out-of-bounds Write SNYK-ALPINE314-ZLIB-2976174	714
	Use After Free SNYK-ALPINE314-BUSYBOX-1920713	614
	Double Free SNYK-ALPINE314-OPENSSL-3314653	614
	Improper Certificate Validation SNYK-ALPINE314-OPENSSL-3368739	614
	Out-of-bounds Write SNYK-ALPINE314-ZLIB-2434419	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:

🦉 Double Free
🦉 Use After Free

[secure-code-warrior-for-github]

Micro-Learning Topic: Double free (Detected by phrase)

Matched on "Double Free"

What is this? (2min video)

Double free errors occur when free() is called more than once with the same memory address as an argument.

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

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