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.18-bullseye-slim to 18.19.1-bullseye-slim #39

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

Conversation

sr1ch1
Copy link
Owner

@sr1ch1 sr1ch1 commented Feb 18, 2024

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.19.1-bullseye-slim, as this image has only 59 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 400 Improper Verification of Cryptographic Signature
SNYK-DEBIAN11-GNUTLS28-6159417
No Known Exploit
high severity 614 Out-of-bounds Write
SNYK-DEBIAN11-PERL-6085272
No Known Exploit
medium severity 514 Out-of-bounds Read
SNYK-DEBIAN11-TAR-3253527
No Known Exploit
low severity 364 CVE-2023-39804
SNYK-DEBIAN11-TAR-6120424
No Known Exploit
critical severity 500 Integer Overflow or Wraparound
SNYK-DEBIAN11-ZLIB-6008961
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.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 7949595779

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 6916642827: 0.0%
Covered Lines: 103
Relevant Lines: 103

💛 - Coveralls

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.

3 participants