Note:
This project will be discontinued after December 13, 2021. [more]
Product:
Git_large_file_storage
(Git_large_file_storage_project)| Repositories |
Unknown: This might be proprietary software. |
| #Vulnerabilities | 4 |
| Date | Id | Summary | Products | Score | Patch | Annotated |
|---|---|---|---|---|---|---|
| 2020-11-05 | CVE-2020-27955 | Git LFS 2.12.0 allows Remote Code Execution. | Git_large_file_storage | 9.8 | ||
| 2021-01-15 | CVE-2021-21237 | 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... | Git_large_file_storage | 7.8 | ||
| 2022-04-20 | CVE-2022-24826 | On Windows, if Git LFS operates on a malicious repository with a `..exe` file as well as a file named `git.exe`, and `git.exe` is not found in `PATH`, the `..exe` program will be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems. Similarly, if the malicious repository contains files named `..exe` and `cygpath.exe`, and `cygpath.exe` is not found in `PATH`, the `..exe` program will be executed when certain Git LFS commands are run. More generally,... | Git_large_file_storage | 7.8 | ||
| 2017-12-21 | CVE-2017-17831 | GitHub Git LFS before 2.1.1 allows remote attackers to execute arbitrary commands via an ssh URL with an initial dash character in the hostname, located on a "url =" line in a .lfsconfig file within a repository. | Git_large_file_storage | 8.8 |