fix(deps): update git2 to 0.20.4 (libgit2 1.9.2) for security fixes#1733
Open
peaktwilight wants to merge 2 commits intoeza-community:mainfrom
Open
fix(deps): update git2 to 0.20.4 (libgit2 1.9.2) for security fixes#1733peaktwilight wants to merge 2 commits intoeza-community:mainfrom
peaktwilight wants to merge 2 commits intoeza-community:mainfrom
Conversation
Update git2 from 0.20.2 to 0.20.4, which pulls in libgit2-sys 0.18.3+1.9.2 (libgit2 1.9.2). This addresses two security vulnerabilities fixed in libgit2 1.9.2: 1. SSH arbitrary command execution: remote repository names were improperly sent to the shell without quoting when using external SSH transport, allowing arbitrary command execution. 2. SSH public key buffer overflow: public keys that are not NUL-terminated were improperly zeroed using memset with the wrong length, resulting in a buffer overflow or incomplete key zeroing. Ref: https://github.com/libgit2/libgit2/releases/tag/v1.9.2 Ref: https://libgit2.org/security/
peaktwilight
force-pushed
the
fix/update-libgit2-security
branch
from
41250ab to
38f2b0a
Compare
Author
|
Note on CI: The The fix for This PR only changes:
|
vavakado
approved these changes
Mar 13, 2026
cafkafk
requested changes
Mar 16, 2026
Member
cafkafk
left a comment
cafkafk
left a comment
There was a problem hiding this comment.
As the CI check mentions, you have to rebase this interactively to not include unnescessarry merge commits in the history.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Updates
git2from 0.20.2 to 0.20.4, which pulls inlibgit2-sys0.18.3+1.9.2 (libgit2 1.9.2). This addresses two security vulnerabilities fixed in libgit2 1.9.2:SSH arbitrary command execution — Remote repository names were improperly sent to the shell without quoting when using external SSH transport, potentially allowing arbitrary command execution.
SSH public key buffer overflow — Public keys that are not NUL-terminated were improperly zeroed using
memsetwith the wrong length, resulting in a buffer overflow or incomplete key zeroing.Changes:
Cargo.toml: Bumpgit2version requirement from"0.20"to"0.20.4"Cargo.lock:git20.20.2 → 0.20.4,libgit2-sys0.18.2+1.9.1 → 0.18.3+1.9.2References:
Fixes: #1734
How Has This Been Tested?
This is a dependency-only update with no API changes between git2 0.20.2 and 0.20.4. Verified locally that
cargo updateresolves correctly and the lockfile only changes thegit2andlibgit2-sysentries.cargo checkpassesNote: The
security_auditCI job has a pre-existing failure onmaindue toRUSTSEC-2026-0009(time v0.3.44), which is unrelated to this change. See run #22494088282.