Bug 28382 - git-lfs security update CVE-2021-21237
Summary: git-lfs security update CVE-2021-21237
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact: Sec team
URL: https://nvd.nist.gov/vuln/detail/CVE-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-19 14:55 CET by Zombie Ryushu
Modified: 2021-02-19 15:01 CET (History)
1 user (show)

See Also:
Source RPM: git-lfs-2.12.1-1.mga8.src.rpm
CVE: CVE-2021-21237
Status comment:


Attachments

Description Zombie Ryushu 2021-02-19 14:55:17 CET
Git LFS is a command line extension for managing large files with Git. On Windows, if Git LFS operates on a malicious repository with a git.bat or git.exe file in the current directory, that program would be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems. This is the result of an incomplete fix for CVE-2020-27955. This issue occurs because on Windows, Go includes (and prefers) the current directory when the name of a command run does not contain a directory separator. Other than avoiding untrusted repositories or using a different operating system, there is no workaround. This is fixed in v2.13.2.
Zombie Ryushu 2021-02-19 14:55:33 CET

CVE: (none) => CVE-2021-21237

Comment 1 Aurelien Oudelet 2021-02-19 15:01:58 CET
(In reply to Zombie Ryushu from comment #0)
> Windows, if Git LFS operates on a malicious repository with a git.bat or
> git.exe file in the current directory, that program would be executed,
> permitting the attacker to execute arbitrary code. This does not affect Unix
> systems. This is the result of an incomplete fix for CVE-2020-27955. This
> issue occurs because on Windows, Go includes (and prefers) the current
> directory when the name of a command run does not contain a directory
> separator. Other than avoiding untrusted repositories or using a different
> operating system, there is no workaround. This is fixed in v2.13.2.

This does not affect Unix systems.

Bug for Windows systems.

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.