Skip to content

[Snyk] Security upgrade node from 18.17.1 to 18.20.2#6

Open
gideon2023u wants to merge 1 commit intomainfrom
snyk-fix-f650e323451f547b934335dd8a53b2ed
Open

[Snyk] Security upgrade node from 18.17.1 to 18.20.2#6
gideon2023u wants to merge 1 commit intomainfrom
snyk-fix-f650e323451f547b934335dd8a53b2ed

Conversation

@gideon2023u
Copy link
Copy Markdown
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.20.2, as this image has only 180 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
high severity 829 Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-5927132
Mature
high severity 829 Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-5927132
Mature
high severity 829 Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-5927132
Mature
high severity 829 Out-of-bounds Write
SNYK-DEBIAN12-GLIBC-5927132
Mature
high severity 829 Out-of-bounds Write
SNYK-DEBIAN12-LIBWEBP-5893095
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