assisted-installer icon indicating copy to clipboard operation
assisted-installer copied to clipboard

[Snyk] Security upgrade golang from latest to 1.22.4

Open gamli75 opened this issue 1 year ago • 3 comments

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 3 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):

  • vendor/github.com/nxadm/tail/Dockerfile

We recommend upgrading to golang:1.22.4, as this image has only 89 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 Input Validation
SNYK-DEBIAN12-PYTHON311-3325304
  614  
high severity Improper Input Validation
SNYK-DEBIAN12-PYTHON311-3325304
  614  
high severity Untrusted Search Path
SNYK-DEBIAN12-PYTHON311-5853785
  614  
high severity Untrusted Search Path
SNYK-DEBIAN12-PYTHON311-5853785
  614  
high severity Allocation of Resources Without Limits or Throttling
SNYK-DEBIAN12-SYSTEMD-6277507
  614  

[!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:

🦉 Improper Input Validation 🦉 Allocation of Resources Without Limits or Throttling

gamli75 avatar Jul 03 '24 05:07 gamli75

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gamli75

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci[bot] avatar Jul 03 '24 05:07 openshift-ci[bot]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 55.72%. Comparing base (6b015a9) to head (4215e5c). Report is 9 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #870   +/-   ##
=======================================
  Coverage   55.72%   55.72%           
=======================================
  Files          15       15           
  Lines        3207     3207           
=======================================
  Hits         1787     1787           
  Misses       1248     1248           
  Partials      172      172           

codecov[bot] avatar Jul 03 '24 05:07 codecov[bot]

@gamli75: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/edge-lint 4215e5c50dcb6653281e6e6a7d897e9c18623498 link true /test edge-lint

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

openshift-ci[bot] avatar Jul 03 '24 07:07 openshift-ci[bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot avatar Oct 01 '24 09:10 openshift-bot