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 golang from 1.22.2-bullseye to 1.23rc1-bullseye #8208

Merged
merged 1 commit into from
Jul 13, 2024

Conversation

satkunas
Copy link
Contributor

@satkunas satkunas commented Jul 5, 2024

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to fix 5 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

  • containers/pfsetacls/Dockerfile

We recommend upgrading to golang:1.23rc1-bullseye, as this image has only 177 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Improper Verification of Cryptographic Signature
SNYK-DEBIAN11-GNUTLS28-6159417
  614  
high severity Information Exposure
SNYK-DEBIAN11-GNUTLS28-6159419
  614  
high severity Out-of-bounds Write
SNYK-DEBIAN11-LIBSSH2-5861756
  614  
critical severity Cleartext Transmission of Sensitive Information
SNYK-DEBIAN11-CURL-3320493
  500  
critical severity Link Following
SNYK-DEBIAN11-GIT-6846200
  500  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@jrouzierinverse jrouzierinverse merged commit 344cc0d into devel Jul 13, 2024
13 checks passed
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.

4 participants