Skip to content

Add RUSTSEC advisory for git2 #2620

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

Merged
djc merged 3 commits into from
Feb 4, 2026
Merged

Add RUSTSEC advisory for git2 #2620

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6492a11
Add RUSTSEC advisory for git2
BoLu1225 Feb 2, 2026
92d248e
Apply suggestion from @cuviper
BoLu1225 Feb 3, 2026
2a80b76
add informational = "unsound"
BoLu1225 Feb 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions crates/git2/RUSTSEC-0000-0000.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
```toml
[advisory]
id = "RUSTSEC-0000-0000"
package = "git2"
date = "2026-02-02"
url = "https://github.com/rust-lang/git2-rs/pull/1213"
informational = "unsound"
categories = ["memory-corruption"]
keywords = ["undefined-behavior"]

[versions]
patched = [">=0.20.4"]
```
# Potential undefined behavior when dereferencing Buf struct

if we dereference the Buf struct right after calling new() or default() on Buf struct, it passes Null Pointer to the unsafe function slice::from_raw_parts. Based on the safety section documentation of function,
data must be non-null and aligned even for zero-length slices or slices of ZSTs. Thus, passing Null Pointer will lead to undefined behavior.