Skip to content

Advisory for CVE-2025-31130 (weak SHA-1) in gix-features #2268

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

Merged
merged 2 commits into from
Apr 4, 2025

Conversation

EliahKagan
Copy link
Contributor

@EliahKagan EliahKagan commented Apr 4, 2025

This adds a notice for CVE-2025-31130 (GHSA-2frx-2596-x5r6) in gix-features.

Although gix-features is usually used as a "knob" for adjusting features across gix-* crates, as well as being used internally:

  • The functionality replaced to fix the vulnerability was in gix-features.
  • All vulnerable crates depend directly or indirectly on gix-features.

My understanding is that the usual practice for RUSTSEC advisories in such a situation is to have only an advisory for that one crate, as in #1705 (comment). So this adds a RUSTSEC notice only for gix-features. (The published repository-local GHSA, and forthcoming global GHSA, are not limited to one affected crate per advisory, and accordingly list more crates.)
 
As in some past advisories, when a global GHSA is published, I can open another PR to add a reference to that.

cc @Byron @emilazy

This adds a notice for CVE-2025-31130 (GHSA-2frx-2596-x5r6) in
`gix-features`.

Co-authored-by: Emily <hello@emily.moe>
@EliahKagan EliahKagan force-pushed the cve-2025-31130-sha branch from 6d3e204 to 5227ee0 Compare April 4, 2025 04:11
@EliahKagan EliahKagan marked this pull request as ready for review April 4, 2025 04:12
Copy link

@emilazy emilazy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I confirm that I agreed to release the advisory text under CC0 1.0 Universal. Thanks to @EliahKagan and @Byron for making handling this easy and enjoyable!

license = "CC0-1.0"

[affected.functions]
"gix_features::hash::bytes_with_hasher" = ["< 0.41.0"]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason not to list the other I/O hashing functions here? They all call into bytes_with_hasher, but then bytes_with_hasher calls into the methods on Hasher too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks--this is probably just an oversight on my part. I'll look at this shortly and try to improve it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added bytes_of_file and bytes. I'm not sure why I had thought those shouldn't be listed in affected.functions, but you are correct that they should be: they are public functions in the affected crate that invoke the vulnerable functionality. Thanks again!

@EliahKagan EliahKagan force-pushed the cve-2025-31130-sha branch from 5227ee0 to 9dda478 Compare April 4, 2025 04:26
@djc djc merged commit 9b45265 into rustsec:main Apr 4, 2025
1 check passed
EliahKagan added a commit to EliahKagan/advisory-db that referenced this pull request Apr 8, 2025
Since it was added in rustsec#2268, RUSTSEC-2025-0021 (CVE-2025-31130) has
an entry in the GitHub Advisory Database. As planned in rustsec#2268, this
adds the link to that global GHSA, as well as to the National
Vulnerability Database entry for the CVE.
djc pushed a commit that referenced this pull request Apr 8, 2025
Since it was added in #2268, RUSTSEC-2025-0021 (CVE-2025-31130) has
an entry in the GitHub Advisory Database. As planned in #2268, this
adds the link to that global GHSA, as well as to the National
Vulnerability Database entry for the CVE.
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.

3 participants