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.15-bullseye-slim to 18.18.2-bullseye-slim #32

Closed
wants to merge 1 commit into from

Conversation

sr1ch1
Copy link
Owner

@sr1ch1 sr1ch1 commented Oct 17, 2023

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.18.2-bullseye-slim, as this image has only 53 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 793 Out-of-bounds Write
SNYK-DEBIAN11-GLIBC-5927133
No Known Exploit
high severity 793 Out-of-bounds Write
SNYK-DEBIAN11-GLIBC-5927133
No Known Exploit
high severity 614 Out-of-bounds Read
SNYK-DEBIAN11-NCURSES-2767191
No Known Exploit
medium severity 621 HTTP Request Smuggling
SNYK-UPSTREAM-NODE-5741793
Proof of Concept
medium severity 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

@sr1ch1 sr1ch1 closed this Nov 18, 2023
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