[Snyk] Security upgrade nginx from 1.19.3-alpine to 1.25.4-alpine

[ekmixon]

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

• devenv/docker/blocks/prometheus_basic_auth_proxy/Dockerfile

We recommend upgrading to nginx:1.25.4-alpine, 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
	714	Out-of-bounds Read SNYK-ALPINE312-APKTOOLS-1533753	No Known Exploit
	714	Double Free SNYK-ALPINE312-CURL-1585256	No Known Exploit
	714	Double Free SNYK-ALPINE312-CURL-1585256	No Known Exploit
	714	Out-of-bounds Write SNYK-ALPINE312-FREETYPE-2809179	No Known Exploit
	714	Buffer Overflow SNYK-ALPINE312-OPENSSL-1569452	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.

[secure-code-warrior-for-github]

Micro-Learning Topic: Buffer overflow (Detected by phrase)

Matched on "Buffer Overflow"

What is this? (2min video)

A buffer overflow condition exists when a program attempts to put more data in a buffer than it can hold or when a program attempts to put data in a memory area past a buffer.

Try a challenge in Secure Code Warrior

Micro-Learning Topic: Double free (Detected by phrase)

Matched on "Double Free"

What is this? (2min video)

Double free errors occur when free() is called more than once with the same memory address as an argument.

Try a challenge in Secure Code Warrior

[sourcery-ai]

PR Type: Enhancement

PR Summary: This pull request addresses the need to update the Docker base image for the prometheus_basic_auth_proxy from nginx version 1.19.3-alpine to 1.25.4-alpine. The primary goal of this update is to mitigate known vulnerabilities present in the older version of the nginx image by moving to a version with no known vulnerabilities.

Decision: Comment

📝 Type: 'Enhancement' - not supported yet.

• Sourcery currently only approves 'Typo fix' PRs.

✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.

No details provided.

✅ Small diff: the diff is small enough to approve with confidence.

No details provided.

General suggestions:

• Ensure thorough testing in a staging environment to confirm that the nginx update does not introduce any regressions or compatibility issues with the current setup.
• Consider reviewing the nginx change logs between these two versions for any deprecated features or significant changes that might affect the application.
• After merging, closely monitor the application's performance and functionality to quickly identify and address any issues that may arise from this update.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

• X
• Mastodon
• LinkedIn
• Facebook

---

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

[guardrails]

⚠️ We detected 1 security issue in this pull request:

Insecure Access Control (1)

Severity	Details	Docs
High	Title: Missing User Instruction grafana/devenv/docker/blocks/prometheus_basic_auth_proxy/Dockerfile Line 1 in cb183ed FROM nginx:1.25.4-alpine	📚

More info on how to fix Insecure Access Control in Dockerfile.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[secure-code-warrior-for-github]

Micro-Learning Topic: Insufficient access control (Detected by phrase)

Matched on "Insecure Access Control"

Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users' accounts, view sensitive files, modify other users’ data, change access rights, etc. Source: https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project

Try a challenge in Secure Code Warrior