fix(deps): update rust crate git2 to 0.21 [security]#127
Open
ferrlabs-renovate[bot] wants to merge 1 commit into
Open
fix(deps): update rust crate git2 to 0.21 [security]#127ferrlabs-renovate[bot] wants to merge 1 commit into
ferrlabs-renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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
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.
This PR contains the following updates:
0.20→0.21Potential undefined behavior when calling Remote::list()
RUSTSEC-2026-0183
More information
Details
When calling
Remote::list()for a remote of a git repository, when that remote does not advertise any references, git2 passes a null pointer to the unsafe functionslice::from_raw_parts(). Based on the safety section documentation of function, data must be non-null even for slices of length zero. Thus, the use of a null pointer leads to undefined behavior.Severity
Unknown
References
This data is provided by OSV and the Rust Advisory Database (CC0 1.0).
Potential undefined behavior with Signature from a buffer-created BlameHunk
RUSTSEC-2026-0184
More information
Details
When a
Blameis created viaBlame::blame_buffer(), and aBlameHunkis retrieved, the pointers to the original author, original committer, final author, and final committer may be null if unavailable. The correspondingBlameHunkmethods then createSignatures based on null pointers; attempting to access the data of theSignatures leads to dereferencing null pointers.Severity
Unknown
References
This data is provided by OSV and the Rust Advisory Database (CC0 1.0).
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate.