GitPython before 3.1.51 Command Injection via unguarded Git options
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| gitpython-developers | GitPython | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Gitpython-developers | Gitpython |
|
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4872-1 | python-git security update |
Github GHSA |
GHSA-956x-8gvw-wg5v | GitPython: command injection via unguarded Git options in `Repo.archive()`, `git.ls_remote()`, and arbitrary file overwrite via `Repo.iter_commits()` / `Repo.blame()` |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.3% (1.251% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitpython Project
Gitpython Project gitpython |
|
| CPEs | cpe:2.3:a:gitpython_project:gitpython:*:*:*:*:*:python:*:* | |
| Vendors & Products |
Gitpython Project
Gitpython Project gitpython |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-88 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitpython-developers
Gitpython-developers gitpython |
|
| Vendors & Products |
Gitpython-developers
Gitpython-developers gitpython |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | GitPython before 3.1.51 fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.ls_remote(), allowing command injection via options such as --exec/--upload-pack (leading to arbitrary command execution). Additionally, Repo.iter_commits() and Repo.blame() do not check for leading-dash revision arguments, so a revision like --output=<path> can cause Git to open and truncate an arbitrary file. Exploitation requires an application that passes attacker-controlled arguments to these methods. | |
| Title | GitPython before 3.1.51 Command Injection via unguarded Git options | |
| Weaknesses | CWE-77 | |
| References |
| |
| Metrics |
cvssV3_1
|