[Snyk] Security upgrade alpine from 3.14.2 to 3.16.7

[ekmixon]

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

• packaging/docker/Dockerfile

We recommend upgrading to alpine:3.16.7, as this image has only 0 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
	400	Use After Free SNYK-ALPINE314-BUSYBOX-1920734	No Known Exploit
	400	Use After Free SNYK-ALPINE314-BUSYBOX-1920755	No Known Exploit
	400	CVE-2022-28391 SNYK-ALPINE314-BUSYBOX-2440608	No Known Exploit
	400	Access of Resource Using Incompatible Type ('Type Confusion') SNYK-ALPINE314-OPENSSL-3314646	No Known Exploit
	500	Out-of-bounds Write SNYK-ALPINE314-ZLIB-2976174	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:

🦉 Use After Free

[secure-code-warrior-for-github]

Micro-Learning Topic: Type confusion (Detected by phrase)

Matched on "Type Confusion"

What is this? (2min video)

When attackers are able to manipulate the memory reserved for objects directly, they can then pass a reference to a crafted block of memory to be used in the place of a valid object type. This triggers the run time engine to execute arbitrary code which is under the control of the attacker due to the induced type confusion.

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