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

[New git version] v2.48.1 #5363

Open
github-actions bot opened this issue Jan 15, 2025 · 12 comments · May be fixed by #5411
Open

[New git version] v2.48.1 #5363

github-actions bot opened this issue Jan 15, 2025 · 12 comments · May be fixed by #5411

Comments

@github-actions
Copy link

https://github.com/git/git/releases/tag/v2.48.1

@bricss
Copy link

bricss commented Jan 20, 2025

Cannot wait to shot 💉 it down straight into my twister 🪢 pair 🙄

@steinybot
Copy link

I'm interested in this to avoid https://nvd.nist.gov/vuln/detail/CVE-2024-52006. I know that is marked as low but given the prevalence of other high vulnerabilities found in the Clone2Leak research, I suspect that there could be other vulnerabilities which this could prevent.

@jeremyd2019
Copy link

Wasn't that fix backported into 2.47.1.2?

@steinybot
Copy link

Wasn't that fix backported into 2.47.1.2?

No I don't think so. It was backported to 2.47.2.

@rimrul
Copy link
Member

rimrul commented Jan 31, 2025

Wasn't that fix backported into 2.47.1.2?

No I don't think so. It was backported to 2.47.2.

The linked release notes mention that CVE number under "Bug Fixes".

@dscho
Copy link
Member

dscho commented Jan 31, 2025

Indeed, CVE-2024-52006 was addressed in v2.47.1(2), along with four other CVEs.

Technically, it is not even correct to say that the fix was backported from v2.47.2 because Git for Windows v2.47.1(2) was built (and distributed to stakeholders well in advance of the public release) waaay before Git v2.47.2 was tagged.

@bricss
Copy link

bricss commented Feb 4, 2025

@dscho any ETA 🗓️ when new 🆕 release may drop? 🙄

@dscho
Copy link
Member

dscho commented Feb 4, 2025

@bricss nope, still busy with other things.

@dscho
Copy link
Member

dscho commented Feb 6, 2025

I actually have the PR branch ready, but needed to do some clean-up first (which I hope to merge tomorrow). My best bet is that Git for Windows v2.48.1 will be released this coming Monday or Tuesday.

@dscho
Copy link
Member

dscho commented Feb 6, 2025

I actually have the PR branch ready,

And just as a side note: since there are no functional changes between the current main and that PR branch, the current snapshot is basically as good as v2.48.1 will be.

@bricss
Copy link

bricss commented Feb 10, 2025

@dscho FYI ℹ️

Due to a range of bad regressions in the curl 8.12.0 release, we are working on getting a patch release out. curl 8.12.1 ships on February 13 and contains a set of bugfixes.

curl/curl#16259

@dscho
Copy link
Member

dscho commented Feb 10, 2025

@bricss wow, thank you so much for paying attention and giving me a heads-up!

@dscho dscho linked a pull request Feb 10, 2025 that will close this issue
@dscho dscho linked a pull request Feb 10, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants