#17980 closed enhancement (fixed)
git-2.40.1
Reported by: | Douglas R. Reno | Owned by: | Tim Tassonis |
---|---|---|---|
Priority: | elevated | Milestone: | 12.0 |
Component: | BOOK | Version: | git |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
New point version, a security release
From the mail to oss-security:
A maintenance release Git v2.40.1, together with releases for older maintenance tracks v2.39.3, v2.38.5, v2.37.7, v2.36.6, v2.35.8, v2.34.8, v2.33.8, v2.32.7, v2.31.8, and v2.30.9, are now available at the usual places. These maintenance releases are to address security issues identified as CVE-2023-25652, CVE-2023-25815, and CVE-2023-29007. They affect ranges of existing versions and users are encouraged to upgrade. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.40.1' tag, as well as the tags for older maintenance tracks listed above: url = https://git.kernel.org/pub/scm/git/git url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://github.com/gitster/git The addressed issues are: * CVE-2023-25652: By feeding specially crafted input to `git apply --reject`, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). * CVE-2023-25815: When Git is compiled with runtime prefix support and runs without translated messages, it still used the gettext machinery to display messages, which subsequently potentially looked for translated messages in unexpected places. This allowed for malicious placement of crafted messages. * CVE-2023-29007: When renaming or deleting a section from a configuration file, certain malicious configuration values may be misinterpreted as the beginning of a new configuration section, leading to arbitrary configuration injection.
Note:
See TracTickets
for help on using tickets.
Seems, nobody wants to take that due to the required advisory...