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 nginx from 1.25.3 to 1.25.5 #195

Closed
wants to merge 1 commit into from

Conversation

micahg
Copy link
Owner

@micahg micahg commented Apr 25, 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

  • packages/mui/Dockerfile

We recommend upgrading to nginx:1.25.5, as this image has only 98 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 Resource Exhaustion
SNYK-DEBIAN12-EXPAT-6227597
No Known Exploit
low severity 436 CVE-2024-2961
SNYK-DEBIAN12-GLIBC-6617103
No Known Exploit
low severity 436 CVE-2024-2961
SNYK-DEBIAN12-GLIBC-6617103
No Known Exploit
high severity 400 Allocation of Resources Without Limits or Throttling
SNYK-DEBIAN12-SYSTEMD-6277507
No Known Exploit
critical severity 500 Integer Overflow or Wraparound
SNYK-DEBIAN12-ZLIB-6008963
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:

🦉 Resource Exhaustion
🦉 Allocation of Resources Without Limits or Throttling

@micahg micahg closed this Apr 27, 2024
@micahg micahg deleted the snyk-fix-734f69286257c0893df03273568967b7 branch July 14, 2024 23:08
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