CVE-2022-36069 json
Poetry Argument Injection vulnerability can lead to local Code Execution
published 2022-09-07 4 y ago modified 2026-06-17 4 mo ago also GHSA-9xgj-fcgf-x6mw , PYSEC-2022-266 , EUVD-2022-0204
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi poetry 1.1.9
- python-poetry poetry 1.1.9
- poetry-core Debian 14, Debian 13, Debian 12 1.0.7-1
debian advisories DEBIAN-CVE-2022-36069
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-36069 updated cvss 7.3
python-poetry: Argument Injection can lead to Local Code Execution
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
1.32% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/python-poetry/poetry/security/advisories/GHSA-9xgj-fcgf-x6mw referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | poetry | <1.1.9 |
1.1.9 |
Affected products
- python-poetry poetry
Classification
References
-
github.com
/python-poetry/poetry/security/advisories/GHSA-9xgj-fcgf-x6mw
web, exploit, vendor-advisory, advisory
-
github.com
/python-poetry/poetry/releases/tag/1.1.9
web, release-notes
-
github.com
/python-poetry/poetry/releases/tag/1.2.0b1
web, release-notes
- sonarsource.com /blog/securing-developer-tools-package-managers/
-
nvd.nist.gov
/vuln/detail/CVE-2022-36069
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/poetry/PYSEC-2022-266.yaml
web
-
github.com
/python-poetry/poetry
package
-
sonarsource.com
/blog/securing-developer-tools-package-managers
web
Sources
- CVE List CVE-2022-36069
- GitHub Advisory GHSA-9xgj-fcgf-x6mw
- NVD CVE-2022-36069
- OSV PYSEC-2022-266
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.