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 18.13.0 to 18.17.1 #12

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

Conversation

sathishcyberintelsysnew
Copy link
Owner

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:18.17.1, as this image has only 147 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 Exposure of Resource to Wrong Sphere
SNYK-DEBIAN11-CURL-3065656
No Known Exploit
critical severity 714 Integer Overflow or Wraparound
SNYK-DEBIAN11-GIT-3232722
No Known Exploit
critical severity 714 Integer Overflow or Wraparound
SNYK-DEBIAN11-GIT-3232724
No Known Exploit
medium severity 686 Improper Resource Shutdown or Release
SNYK-DEBIAN11-IMAGEMAGICK-3314439
Mature
medium severity 686 CVE-2022-44268
SNYK-DEBIAN11-IMAGEMAGICK-3314444
Mature

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