Skip to content

[Snyk] Security upgrade nginx from latest to 1.23#12

Open
baby636 wants to merge 1 commit intomasterfrom
snyk-fix-346d40e33840771cbae7a27dffd4d8b2
Open

[Snyk] Security upgrade nginx from latest to 1.23#12
baby636 wants to merge 1 commit intomasterfrom
snyk-fix-346d40e33840771cbae7a27dffd4d8b2

Conversation

@baby636
Copy link
Copy Markdown
Owner

@baby636 baby636 commented Feb 4, 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 nginx:1.23, as this image has only 80 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
critical severity 714 Exposure of Resource to Wrong Sphere
SNYK-DEBIAN11-CURL-3065656
No Known Exploit
critical severity 714 Exposure of Resource to Wrong Sphere
SNYK-DEBIAN11-CURL-3065656
No Known Exploit
high severity 400 Cleartext Transmission of Sensitive Information
SNYK-DEBIAN11-CURL-3179181
No Known Exploit
high severity 400 Numeric Errors
SNYK-DEBIAN11-TIFF-3113871
No Known Exploit
high severity 400 Use After Free
SNYK-DEBIAN11-TIFF-3252499
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.

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