CVE-2022-36069: Poetry is a dependency manager for Python. When handling dependencies that come from a Git repository instead of a registry, Poetry uses various comma...

Description

Poetry is a dependency manager for Python. 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. Versions 1.1.9 and 1.2.0b1 contain patches for this issue.

Metrics

CVSS 3.1

7.3/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS Probability

1.46%

70.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions	Update
Python-Poetry	Poetry	< 1.1.9	—
Python-Poetry	Poetry	1.2.0	Alpha1

References

https://github.com/python-poetry/poetry/releases/tag/1.1.9Release Notes
https://github.com/python-poetry/poetry/releases/tag/1.2.0b1Release Notes
https://github.com/python-poetry/poetry/security/advisories/GHSA-9xgj-fcgf-x6mwExploit, Vendor Advisory
https://www.sonarsource.com/blog/securing-developer-tools-package-managers/
https://github.com/python-poetry/poetry/releases/tag/1.1.9Release Notes
https://github.com/python-poetry/poetry/releases/tag/1.2.0b1Release Notes
https://github.com/python-poetry/poetry/security/advisories/GHSA-9xgj-fcgf-x6mwExploit, Vendor Advisory
https://www.sonarsource.com/blog/securing-developer-tools-package-managers/

Timeline

Published: Sep 7, 2022
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2022-36069?

Poetry is a dependency manager for Python. 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. Versions 1.1.9 and 1.2.0b1 contain patches for this issue.

How severe is CVE-2022-36069?

CVE-2022-36069 has a CVSS score of 7.3/10 (HIGH severity). The EPSS model estimates a 1.46% probability of exploitation in the next 30 days.

How do I fix CVE-2022-36069?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.