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 alpine to 1.25.3-alpine3.18 #59

Closed

Conversation

yaswanth-deriv
Copy link
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 nginx:1.25.3-alpine3.18, as this image has only 0 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 Out-of-bounds Read
SNYK-ALPINE318-LIBX11-6042396
No Known Exploit
medium severity 514 Loop with Unreachable Exit Condition ('Infinite Loop')
SNYK-ALPINE318-LIBX11-6042397
No Known Exploit
high severity 614 Integer Overflow or Wraparound
SNYK-ALPINE318-LIBX11-6042398
No Known Exploit
medium severity 514 Improper Check for Unusual or Exceptional Conditions
SNYK-ALPINE318-OPENSSL-6055795
No Known Exploit
medium severity 514 Improper Check for Unusual or Exceptional Conditions
SNYK-ALPINE318-OPENSSL-6055795
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.

Copy link

github-actions bot commented Feb 1, 2024

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Feb 1, 2024
Copy link

github-actions bot commented Feb 7, 2024

This PR was closed because it has been stalled for 5 days with no activity. Please reopen it if needed.

@github-actions github-actions bot closed this Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants