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 [affected.functions] in gix-worktree-state advisory #2195

Merged
merged 1 commit into from
Jan 18, 2025

Conversation

Shnatsel
Copy link
Member

@Shnatsel Shnatsel commented Jan 18, 2025

I clicked "merge" too quickly, oops

But it's okay since the advisory is not yet live

I clicked "merge" too quickly, oops
@Shnatsel Shnatsel merged commit d3d1ba6 into main Jan 18, 2025
1 check passed
EliahKagan added a commit to EliahKagan/advisory-db that referenced this pull request Jan 18, 2025
When including information about affected functions in advisory
metadata, I have used `"*"` in a few advisories when the bounds
were no narrower than the bounds for the vulnerability. But
specific are still needed or preferred in that situation.

This replaces `"*"` in those advisories with more specific bounds.
(For rustsec#2193, this has already been done in rustsec#2195.)

See discussion in:
rustsec#2193 (review)
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.

1 participant