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 alpine from 3.14.2 to 3.16.7 #492

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ekmixon
Copy link
Owner

@ekmixon ekmixon commented Oct 26, 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

  • packages/grafana-toolkit/docker/grafana-plugin-ci-alpine/Dockerfile

We recommend upgrading to alpine:3.16.7, 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
high severity 614 Use After Free
SNYK-ALPINE314-BUSYBOX-1920713
No Known Exploit
high severity 614 Use After Free
SNYK-ALPINE314-BUSYBOX-1920718
No Known Exploit
high severity 614 Use After Free
SNYK-ALPINE314-BUSYBOX-1920734
No Known Exploit
high severity 614 Use After Free
SNYK-ALPINE314-BUSYBOX-1920744
No Known Exploit
critical severity 714 Out-of-bounds Write
SNYK-ALPINE314-ZLIB-2976174
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:

🦉 Use After Free

@secure-code-warrior-for-github

Micro-Learning Topic: Use-after-free (Detected by phrase)

Matched on "Use After Free"

What is this? (2min video)

Dereferencing pointers to objects that have already been freed opens the door to execution of arbitrary code. Attackers may be able to insert instructions at the freed memory location in order to trigger the exploit when the pointer is used after the memory has been freed.

Try a challenge in Secure Code Warrior

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