Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade node from 16.0.0-buster to 16.14.2-buster #67

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jalane81
Copy link

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.14.2-buster, as this image has only 439 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
critical severity 714 Buffer Overflow
SNYK-DEBIAN10-OPENSSL-1569403
No Known Exploit
high severity 614 Out-of-bounds Read
SNYK-DEBIAN10-OPENSSL-1569406
No Known Exploit
high severity 614 Loop with Unreachable Exit Condition ('Infinite Loop')
SNYK-DEBIAN10-OPENSSL-2426310
No Known Exploit
critical severity 786 OS Command Injection
SNYK-DEBIAN10-OPENSSL-2807585
No Known Exploit
high severity 614 Use After Free
SNYK-DEBIAN10-SUBVERSION-2635642
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants