Bug 31856

Summary: git new security issues CVE-2023-25652, CVE-2023-25815, CVE-2023-29007
Product: Mageia Reporter: David Walser <luigiwalser>
Component: SecurityAssignee: QA Team <qa-bugs>
Status: RESOLVED FIXED QA Contact: Sec team <security>
Severity: normal    
Priority: Normal CC: andrewsfarm, davidwhodgins, herman.viaene, mageia, sysadmin-bugs
Version: 8Keywords: advisory, validated_update
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: MGA8-64-OK
Source RPM: git-2.30.8-1.mga8.src.rpm CVE:
Status comment:

Description David Walser 2023-05-01 16:50:59 CEST 
Git 2.30.9 has been released on April 25, fixing security issues:
https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.30.9.txt
https://lore.kernel.org/git/xmqqa5yv3n93.fsf@gitster.g/T/

Updated package uploaded for Mageia 8.

Advisory:
========================

Updated git packages fix security vulnerabilities:

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-25652).

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-25815).

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
(CVE-2023-29007).

References:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-25652
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-25815
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-29007
https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.30.9.txt
https://lore.kernel.org/git/xmqqa5yv3n93.fsf@gitster.g/T/
========================

Updated packages in core/updates_testing:
========================
git-2.30.9-1.mga8
git-arch-2.30.9-1.mga8
git-core-2.30.9-1.mga8
git-core-oldies-2.30.9-1.mga8
git-cvs-2.30.9-1.mga8
git-email-2.30.9-1.mga8
git-prompt-2.30.9-1.mga8
git-subtree-2.30.9-1.mga8
git-svn-2.30.9-1.mga8
gitk-2.30.9-1.mga8
gitweb-2.30.9-1.mga8
lib(64)git-devel-2.30.9-1.mga8
perl-Git-2.30.9-1.mga8
perl-Git-SVN-2.30.9-1.mga8

from SRPM:
git-2.30.9-1.mga8.src.rpm
PC LX 2023-05-01 20:44:14 CEST

CC: (none) => mageia

Comment 1 Herman Viaene 2023-05-03 13:50:38 CEST 
MGA8-64 MATE on Acer Aspire 5253
No installation issues
After removing the previous .git folder from my home, followed procedure as in bug 31553.
$ git init
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: 
hint: 	git config --global init.defaultBranch <name>
hint: 
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint: 
hint: 	git branch -m <name>
Initialized empty Git repository in /home/tester8/.git/
[tester8@mach7 ~ (master)]$ git config --global user.name "tester8"
[tester8@mach7 ~ (master)]$ git config --global user.email "herman.viaene@hotmail.be"
[tester8@mach7 ~ (master)]$ git add ~/Documents/exo.txt
[tester8@mach7 ~ (master)]$ git branch
[tester8@mach7 ~ (master)]$ git show
fatal: your current branch 'master' does not have any commits yet
[tester8@mach7 ~ (master)]$ git commit
[master (root-commit) da05385] test git2.39
 1 file changed, 1293 insertions(+)
 create mode 100644 Documents/exo.txt
[tester8@mach7 ~ (master)]$ git show
commit da05385f951897141cfbf13f84b003d5b5a12e18 (HEAD -> master)
Author: tester8 <herman.viaene@hotmail.be>
Date:   Wed May 3 13:46:01 2023 +0200

    test git2.39

diff --git a/Documents/exo.txt b/Documents/exo.txt
new file mode 100644
index 0000000..3902b92
--- /dev/null
+++ b/Documents/exo.txt
@@ -0,0 +1,1293 @@
+execve("/usr/bin/thunar", ["thunar"], 0x7ffc418dda20 /* 68 vars */) = 0
+brk(NULL)                               = 0xf1e000
+access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
+openat(AT_FDCWD, "/usr/lib64/tls/x86_64/x86_64/libthunarx-3.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
and the rest of the text.
Good to go.

Whiteboard: (none) => MGA8-64-OK
CC: (none) => herman.viaene

Comment 2 Thomas Andrews 2023-05-04 21:20:14 CEST 
Thank you, Herman. Validating. Advisory in comment 0.

CC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => validated_update

Dave Hodgins 2023-05-06 18:27:25 CEST

Keywords: (none) => advisory
CC: (none) => davidwhodgins

Comment 3 Mageia Robot 2023-05-06 20:20:45 CEST 
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2023-0163.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED