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

fix(deps): update module github.com/go-git/go-git/v5 to v5.11.0 [security] #22

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 9, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/go-git/go-git/v5 v5.0.0 -> v5.11.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2023-49568

Impact

A denial of service (DoS) vulnerability was discovered in go-git versions prior to v5.11. This vulnerability allows an attacker to perform denial of service attacks by providing specially crafted responses from a Git server which triggers resource exhaustion in go-git clients.

Applications using only the in-memory filesystem supported by go-git are not affected by this vulnerability.
This is a go-git implementation issue and does not affect the upstream git cli.

Patches

Users running versions of go-git from v4 and above are recommended to upgrade to v5.11 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is not possible, we recommend limiting its use to only trust-worthy Git servers.

Credit

Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.

References

CVE-2023-49569

Impact

A path traversal vulnerability was discovered in go-git versions prior to v5.11. This vulnerability allows an attacker to create and amend files across the filesystem. In the worse case scenario, remote code execution could be achieved.

Applications are only affected if they are using the ChrootOS, which is the default when using "Plain" versions of Open and Clone funcs (e.g. PlainClone). Applications using BoundOS or in-memory filesystems are not affected by this issue.
This is a go-git implementation issue and does not affect the upstream git cli.

Patches

Users running versions of go-git from v4 and above are recommended to upgrade to v5.11 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is not possible in a timely manner, we recommend limiting its use to only trust-worthy Git servers.

Credit

Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.


Release Notes

go-git/go-git (github.com/go-git/go-git/v5)

v5.11.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.10.1...v5.11.0

v5.10.1

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.10.0...v5.10.1

v5.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.9.0...v5.10.0

v5.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.8.1...v5.9.0

v5.8.1

Compare Source

What's Changed

Full Changelog: go-git/go-git@v5.8.0...v5.8.1

v5.8.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.7.0...v5.7.1

v5.7.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.6.1...v5.7.0

v5.6.1

Compare Source

What's Changed

Full Changelog: go-git/go-git@v5.6.0...v5.6.1

v5.6.0

Compare Source

What's Changed

Full Changelog: go-git/go-git@v5.5.2...v5.6.0

v5.5.2

Compare Source

What's Changed

Full Changelog: go-git/go-git@v5.5.1...v5.5.2

v5.5.1

Compare Source

What's Changed

Full Changelog: go-git/go-git@v5.5.0...v5.5.1

v5.5.0

Compare Source

What's Changed

Full Changelog: go-git/go-git@v5.4.2...v5.5.0

v5.4.2

Compare Source

Change Log

  • Revert "plumbing: format/packfile, prevent large objects from being read into memory completely (#​303) (da81027)

v5.4.1

Compare Source

Change Log

  • remote: patch default timeout for List from 600ms to 10s (#​321)

v5.4.0

Compare Source

Change Log

v5.3.0

Compare Source

Change Log

v5.2.0

Compare Source

Change Log

v5.1.0

Compare Source

This version includes three main relevant features, the long-awaited support for renames on diff by hash and similar content (#​38, #​42), color diff support (#​40), and support for work with git config from different scopes and Worktree.Commit with an empty CommitOptions (#​75)

Change Log

  • Repository.ConfigScoped and Worktree.Commit with empty CommitOptions (#​75)
  • Remote.Push: support force option (#​71)
  • Remote.Fetch: support exact SHA1 refspecs (#​58)
  • plumbing: diff, reset color at end of line (#​66)
  • plumbing: object, Commit.Patch support to as nil (#​62)
  • plumbing: object, Fixed the ambiguous implicit conversions causing errors while building . (#​57)
  • plumbing: object, make renames diff default (#​42)
  • plumbing: exact renames detection could leave gaps in the changes (#​54)
  • plumbing: diff, add colored output support. (#​40)
  • plumbing: detect renames by hash and similar content in diff tree (#​38)
  • plumbing: transport, fix handling of empty adv-refs on upload-pack (#​22)
  • plumbing: transport server check for nil Packfile, fixes ref deletes (#​11)
  • plumbing/storage: close Reader & Writer of EncodedObject after use (#​73)
  • storage/filesystem: dotgit, sanity check provided reference path (#​39)

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

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.

0 participants