[Snyk] Security upgrade node from 16.13-alpine to 16.19.1-alpine

[thisguy726]

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 node:16.19.1-alpine, as this image has only 13 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	Out-of-bounds Write SNYK-ALPINE315-ZLIB-2976173	No Known Exploit
	621	HTTP Request Smuggling SNYK-UPSTREAM-NODE-3035795	Proof of Concept
	621	HTTP Request Smuggling SNYK-UPSTREAM-NODE-5741793	Proof of Concept
	721	Infinite loop SNYK-UPSTREAM-NODE-5811867	Proof of Concept
	621	Improper Access Control SNYK-UPSTREAM-NODE-5843454	Proof of Concept

---

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:

🦉 Improper Access Control

[sonarqubecloud]

Quality Gate failed

Failed conditions
14 Security Hotspots
D Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[sourcery-ai]

PR Type: Enhancement

PR Summary: This pull request addresses the need to update the Docker base image from node:16.13-alpine to node:16.19.1-alpine in order to mitigate known vulnerabilities associated with the older version. By upgrading to node:16.19.1-alpine, the project benefits from security fixes and reduced vulnerability exposure as highlighted by the automated analysis. The changes are confined to the Dockerfile, specifically updating the base and production image versions.

Decision: Comment

📝 Type: 'Enhancement' - not supported yet.

• Sourcery currently only approves 'Typo fix' PRs.

✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.

No details provided.

✅ Small diff: the diff is small enough to approve with confidence.

No details provided.

General suggestions:

• Ensure thorough testing of the application with the new Docker base image to confirm that the upgrade does not introduce any breaking changes or unexpected behavior.
• Consider reviewing and updating the documentation to reflect the changes in the base image and any new requirements or considerations that come with it.
• Given the security context of this update, it might be beneficial to establish a regular schedule for reviewing and updating dependencies and base images to proactively manage vulnerabilities.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

• X
• Mastodon
• LinkedIn
• Facebook

---

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.