Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk: High] Gitpython (Due 09/30/23) #5878

Closed
Tracked by #137
cnlucas opened this issue Aug 30, 2023 · 0 comments · Fixed by #5907
Closed
Tracked by #137

[Snyk: High] Gitpython (Due 09/30/23) #5878

cnlucas opened this issue Aug 30, 2023 · 0 comments · Fixed by #5907
Assignees
Labels
Security: general General security concern or issue Security: high Remediate within 30 days Work: Back-end
Milestone

Comments

@cnlucas
Copy link
Member

cnlucas commented Aug 30, 2023

Gitpython -Untrusted Search Path

Introduced through
gitpython@3.1.32
Fixed in
gitpython@3.1.33

Exploit maturity
Proof of Concept

Detailed paths and remediation

Introduced through: project@0.0.0 › gitpython@3.1.32
Fix: Upgrade gitpython to version 3.1.33

Security information
Factors contributing to the scoring:

Snyk: [CVSS 7.8](https://security.snyk.io/vuln/SNYK-PYTHON-GITPYTHON-5871282) - High Severity
NVD: Not available. NVD has not yet published its analysis.

Why are the scores different? Learn how Snyk evaluates vulnerability scores
Overview

GitPython is a python library used to interact with Git repositories

Affected versions of this package are vulnerable to Untrusted Search Path allowing an attacker to run any arbitrary commands through a downloaded repository with a malicious git executable.

Note: This vulnerability affects only Windows systems.

Completion Criteria
[ ] We have either upgraded and removed the vulnerability, or determined we are not affected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Security: general General security concern or issue Security: high Remediate within 30 days Work: Back-end
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants