Lucene search

K
slackwareSlackware Linux ProjectSSA-2024-136-02
HistoryMay 16, 2024 - 2:33 a.m.

[slackware-security] git

2024-05-1602:33:18
Slackware Linux Project
www.slackware.com
5
slackware
git
security fix
case confusion
arbitrary code
cloning
cve-2024-32002
cve-2024-32004
cve-2024-32020
cve-2024-32021
cve-2024-32465

9 High

CVSS3

Attack Vector

NETWORK

Attack Complexity

HIGH

Privileges Required

NONE

User Interaction

NONE

Scope

CHANGED

Confidentiality Impact

HIGH

Integrity Impact

HIGH

Availability Impact

HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

7.8 High

AI Score

Confidence

Low

0.001 Low

EPSS

Percentile

40.2%

New git packages are available for Slackware 15.0 and -current to
fix security issues.

Here are the details from the Slackware 15.0 ChangeLog:

patches/packages/git-2.39.4-i586-1_slack15.0.txz: Upgraded.
This update fixes security issues:
Recursive clones on case-insensitive filesystems that support symbolic
links are susceptible to case confusion that can be exploited to
execute just-cloned code during the clone operation.
Repositories can be configured to execute arbitrary code during local
clones. To address this, the ownership checks introduced in v2.30.3
are now extended to cover cloning local repositories.
Local clones may end up hardlinking files into the target repository’s
object database when source and target repository reside on the same
disk. If the source repository is owned by a different user, then
those hardlinked files may be rewritten at any point in time by the
untrusted user.
When cloning a local source repository that contains symlinks via the
filesystem, Git may create hardlinks to arbitrary user-readable files
on the same filesystem as the target repository in the objects/
directory.
It is supposed to be safe to clone untrusted repositories, even those
unpacked from zip archives or tarballs originating from untrusted
sources, but Git can be tricked to run arbitrary code as part of the
clone.
For more information, see:
https://vulners.com/cve/CVE-2024-32002
https://vulners.com/cve/CVE-2024-32004
https://vulners.com/cve/CVE-2024-32020
https://vulners.com/cve/CVE-2024-32021
https://vulners.com/cve/CVE-2024-32465
(* Security fix *)

Where to find the new packages:

Thanks to the friendly folks at the OSU Open Source Lab
(http://osuosl.org) for donating FTP and rsync hosting
to the Slackware project! :-)

Also see the “Get Slack” section on http://slackware.com for
additional mirror sites near you.

Updated package for Slackware 15.0:
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/git-2.39.4-i586-1_slack15.0.txz

Updated package for Slackware x86_64 15.0:
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/git-2.39.4-x86_64-1_slack15.0.txz

Updated package for Slackware -current:
ftp://ftp.slackware.com/pub/slackware/slackware-current/slackware/d/git-2.45.1-i586-1.txz

Updated package for Slackware x86_64 -current:
ftp://ftp.slackware.com/pub/slackware/slackware64-current/slackware64/d/git-2.45.1-x86_64-1.txz

MD5 signatures:

Slackware 15.0 package:
837b659cb32a07eed09bf4de30b72741 git-2.39.4-i586-1_slack15.0.txz

Slackware x86_64 15.0 package:
530b3158ef258881e1a340baff5d61b5 git-2.39.4-x86_64-1_slack15.0.txz

Slackware -current package:
0f6950f7d7f336e7aa2d47d4a4711bc9 d/git-2.45.1-i586-1.txz

Slackware x86_64 -current package:
685fddae35e6b5d4366104f1c05ccd43 d/git-2.45.1-x86_64-1.txz

Installation instructions:

Upgrade the package as root:
> upgradepkg git-2.39.4-i586-1_slack15.0.txz

9 High

CVSS3

Attack Vector

NETWORK

Attack Complexity

HIGH

Privileges Required

NONE

User Interaction

NONE

Scope

CHANGED

Confidentiality Impact

HIGH

Integrity Impact

HIGH

Availability Impact

HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

7.8 High

AI Score

Confidence

Low

0.001 Low

EPSS

Percentile

40.2%