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 14.16.1 to 14.21.1 #116

Closed
wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

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

  • superset-websocket/Dockerfile

We recommend upgrading to node:14.21.1, as this image has only 436 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 Directory Traversal
SNYK-DEBIAN9-DPKG-2847943
No Known Exploit
high severity 614 Loop with Unreachable Exit Condition ('Infinite Loop')
SNYK-DEBIAN9-OPENSSL-2426305
No Known Exploit
critical severity 714 OS Command Injection
SNYK-DEBIAN9-OPENSSL-2807589
No Known Exploit
critical severity 714 Buffer Overflow
SNYK-DEBIAN9-PYTHON27-1063180
No Known Exploit
high severity 614 Resource Exhaustion
SNYK-DEBIAN9-PYTHON35-1570179
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.

@stale
Copy link

stale bot commented Feb 14, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive label Feb 14, 2023
@stale stale bot closed this Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant