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鈥檒l 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.16.1-bullseye-slim #23

Closed
wants to merge 1 commit into from

Conversation

sr1ch1
Copy link
Owner

@sr1ch1 sr1ch1 commented Jul 30, 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鈥檒l benefit from security fixes in the latest version of your chosen image.

Changes included in this PR

  • Dockerfile

We recommend upgrading to node:18.16.1-bullseye-slim, as this image has only 50 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
medium severity 514 Denial of Service (DoS)
SNYK-UPSTREAM-NODE-5741792
No Known Exploit
medium severity 621 HTTP Request Smuggling
SNYK-UPSTREAM-NODE-5741793
Proof of Concept
high severity 614 Prototype Pollution
SNYK-UPSTREAM-NODE-5741794
No Known Exploit
medium severity 514 Inconsistency Between Implementation and Documented Design
SNYK-UPSTREAM-NODE-5741796
No Known Exploit
high severity 614 Denial of Service (DoS)
SNYK-UPSTREAM-NODE-5741889
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:

馃 Prototype Pollution
馃 Denial of Service (DoS)

@sr1ch1 sr1ch1 closed this Nov 18, 2023
@coveralls
Copy link

Pull Request Test Coverage Report for Build 5703642715

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

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 4990376181: 0.0%
Covered Lines: 101
Relevant Lines: 101

馃挍 - 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.

None yet

3 participants