PyPI: poetry-core
CVE-2022-36069
Safety vulnerability ID: SFTY-20220907-62099
Safety legacy ID: pyup.io-71598
When handling dependencies that come from a Git repository instead of a registry, Poetry uses various commands, such as 'git clone'. These commands are constructed using user input (e.g. the repository URL). When building the commands, Poetry correctly avoids Command Injection vulnerabilities by passing an array of arguments instead of a command string. However, there is the possibility that a user input starts with a dash ('-') and is therefore treated as an optional argument instead of a positional one. This can lead to Code Execution because some of the commands have options that can be leveraged to run arbitrary executables. If a developer is exploited, the attacker could steal credentials or persist their access. If the exploit happens on a server, the attackers could use their access to attack other internal systems. Since this vulnerability requires a fair amount of user interaction, it is not as dangerous as a remotely exploitable one. However, it still puts developers at risk when dealing with untrusted files in a way they think is safe, because the exploit still works when the victim tries to make sure nothing can happen, e.g. by vetting any Git or Poetry config files that might be present in the directory.
Overview
Poetry Argument Injection can lead to Local Code Execution
Advisory
When handling dependencies that come from a Git repository instead of a registry, Poetry uses various commands, such as 'git clone'. These commands are constructed using user input (e.g. the repository URL). When building the commands, Poetry correctly avoids Command Injection vulnerabilities by passing an array of arguments instead of a command string. However, there is the possibility that a user input starts with a dash ('-') and is therefore treated as an optional argument instead of a positional one. This can lead to Code Execution because some of the commands have options that can be leveraged to run arbitrary executables. If a developer is exploited, the attacker could steal credentials or persist their access. If the exploit happens on a server, the attackers could use their access to attack other internal systems. Since this vulnerability requires a fair amount of user interaction, it is not as dangerous as a remotely exploitable one. However, it still puts developers at risk when dealing with untrusted files in a way they think is safe, because the exploit still works when the victim tries to make sure nothing can happen, e.g. by vetting any Git or Poetry config files that might be present in the directory.
How to Fix
Mitigation and Workarounds
---
Vulnerable Functions
Functions linked to known vulnerabilities.
References
- https://getsafety.com/vulnerabilities/SFTY-20220907-62099/CVE-2022-36069
- https://github.com/python-poetry/poetry/security/advisories/GHSA-9xgj-fcgf-x6mw
- https://nvd.nist.gov/vuln/detail/CVE-2022-36069
- https://github.com/pypa/advisory-database/tree/main/vulns/poetry/PYSEC-2022-266.yaml
- https://github.com/python-poetry/poetry/releases/tag/1.1.9
- https://github.com/python-poetry/poetry/releases/tag/1.2.0b1
- https://www.sonarsource.com/blog/securing-developer-tools-package-managers
- https://github.com/advisories/GHSA-9xgj-fcgf-x6mw
Verified by Safety
Our Cybersecurity Intelligence Team reviewed this vulnerability. We combine public data with our own research to find issues not yet reported to public sources.
Learn more
