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 perl version] v5.40.0 #5002

Open
github-actions bot opened this issue Jun 10, 2024 · 3 comments · May be fixed by git-for-windows/MSYS2-packages#178
Open

[New perl version] v5.40.0 #5002

github-actions bot opened this issue Jun 10, 2024 · 3 comments · May be fixed by git-for-windows/MSYS2-packages#178

Comments

@github-actions
Copy link

https://github.com/Perl/perl5/releases/tag/v5.40.0

@dscho
Copy link
Member

dscho commented Jun 10, 2024

There are only two CVEs addressed by this version, the rest is new features (with the potential to introduce regressions, which is why I am hesitant to upgrade to that .0 version):

  • CVE-2023-47038 - Write past buffer end via illegal user-defined Unicode property

    Already addressed in v5.38.1, Git for Windows uses v5.38.2

  • CVE-2023-47039 - Perl for Windows binary hijacking vulnerability

    Git for Windows ships with the MSYS2 variant of Perl, which does not use cmd.exe (but bash.exe) as shell, and even then, MSYS2 side-steps Windows' default path lookup, therefore Git for Windows' variant of Perl is not susceptible to this vulnerability.

Let's wait for Perl 5.40.1, or for a month without any hot bug fix release, whichever comes first. (Leaving this open in case it's the latter.)

@dscho
Copy link
Member

dscho commented Jul 9, 2024

/open pr

The workflow run was started

@dscho
Copy link
Member

dscho commented Jul 15, 2024

There is a hang in CI that I cannot explain, so I will postpone this until after Git for Windows v2.46.0 will be published.

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.

1 participant