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.

Sign up for GitHub

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

Jump to bottom

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

Merged
merged 1 commit into from
Jan 28, 2024
Merged

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

merged 1 commit into from
Jan 28, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 27, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

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

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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

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 has been generated by Mend Renovate. View repository job log here.

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 27, 2023 •
edited
Loading

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@codecov Codecov
Copy link

codecov bot commented Dec 27, 2023 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (502b1ef) 51.85185% compared to head (e3a07f0) 51.41069%.

Additional details and impacted files 
@@                 Coverage Diff                 @@
##              master       #1718         +/-   ##
===================================================
- Coverage   51.85185%   51.41069%   -0.44116%     
===================================================
  Files            413         401         -12     
  Lines          28269       27327        -942     
  Branches         307         307                 
===================================================
- Hits           14658       14049        -609     
+ Misses         12179       11911        -268     
+ Partials        1432        1367         -65
Flag Coverage Δ
cctp-relayer ?
git-changes-action 53.94265% <ø> (ø)
packages 91.02167% <ø> (ø)
promexporter ?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/git-changes-action-go-github.aaakk.us.kg/go-git/go-git/v5-vulnerability branch 3 times, most recently from 8581e45 to e559328 Compare January 14, 2024 21:29
@renovate
fix(deps): update module github.com/go-git/go-git/v5 to v5.11.0 [secu…
e3a07f0 
…rity]

| datasource | package                     | from   | to      |
| ---------- | --------------------------- | ------ | ------- |
| go         | github.com/go-git/go-git/v5 | v5.8.1 | v5.11.0 |


Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/git-changes-action-go-github.aaakk.us.kg/go-git/go-git/v5-vulnerability branch from e559328 to e3a07f0 Compare January 24, 2024 03:32
@trajan0x trajan0x marked this pull request as ready for review January 28, 2024 16:22
@trajan0x trajan0x self-requested a review as a code owner January 28, 2024 16:22
@trajan0x trajan0x merged commit 2db0194 into master Jan 28, 2024
62 checks passed
@trajan0x trajan0x deleted the renovate/git-changes-action-go-github.aaakk.us.kg/go-git/go-git/v5-vulnerability branch January 28, 2024 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@trajan0x trajan0x Awaiting requested review from trajan0x trajan0x is a code owner

Assignees

@trajan0x trajan0x

Labels
dependencies needs-go-generate-contrib/git-changes-action size/s
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@trajan0x