pysec-2022-43179
Vulnerability from pysec
Poetry is a dependency manager for Python. To handle dependencies that come from a Git repository, Poetry executes various commands, e.g. git config. These commands are being executed using the executable’s name and not its absolute path. This can lead to the execution of untrusted code due to the way Windows resolves executable names to paths. Unlike Linux-based operating systems, Windows searches for the executable in the current directory first and looks in the paths that are defined in the PATH environment variable afterward. This vulnerability can lead to Arbitrary Code Execution, which would lead to the takeover of the system. 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. The victim could also not protect themself by vetting any Git or Poetry config files that might be present in the directory, because the behavior is undocumented. Versions 1.1.9 and 1.2.0b1 contain patches for this issue.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "poetry",
"purl": "pkg:pypi/poetry"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.9"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.0",
"0.10.0",
"0.10.0a0",
"0.10.0a1",
"0.10.0a2",
"0.10.0a3",
"0.10.1",
"0.10.2",
"0.10.3",
"0.11.0",
"0.11.0a0",
"0.11.0a1",
"0.11.0a2",
"0.11.0a3",
"0.11.0a4",
"0.11.1",
"0.11.2",
"0.11.3",
"0.11.4",
"0.11.5",
"0.12.0",
"0.12.0a0",
"0.12.0a1",
"0.12.0a2",
"0.12.0a3",
"0.12.0a4",
"0.12.0a5",
"0.12.1",
"0.12.10",
"0.12.11",
"0.12.12",
"0.12.13",
"0.12.14",
"0.12.15",
"0.12.16",
"0.12.17",
"0.12.2",
"0.12.3",
"0.12.4",
"0.12.5",
"0.12.6",
"0.12.7",
"0.12.8",
"0.12.9",
"0.2.0",
"0.3.0",
"0.4.0",
"0.4.0.post1",
"0.4.1",
"0.4.2",
"0.5.0",
"0.5.0b1",
"0.5.0b2",
"0.6.0",
"0.6.1",
"0.6.2",
"0.6.3",
"0.6.3b1",
"0.6.3b2",
"0.6.3b3",
"0.6.3b4",
"0.6.3b5",
"0.6.3b6",
"0.6.3b7",
"0.6.4",
"0.6.4b1",
"0.6.5",
"0.7.0",
"0.7.0b1",
"0.7.0b2",
"0.7.0b3",
"0.7.0b4",
"0.7.1",
"0.8.0",
"0.8.0a0",
"0.8.0a1",
"0.8.0a2",
"0.8.0a3",
"0.8.0a4",
"0.8.1",
"0.8.1a0",
"0.8.2",
"0.8.3",
"0.8.4",
"0.8.5",
"0.8.5a0",
"0.8.6",
"0.9.0",
"0.9.0a0",
"0.9.0a1",
"0.9.0a2",
"0.9.0a3",
"0.9.1",
"1.0.0",
"1.0.0a0",
"1.0.0a1",
"1.0.0a2",
"1.0.0a3",
"1.0.0a4",
"1.0.0a5",
"1.0.0b1",
"1.0.0b2",
"1.0.0b3",
"1.0.0b4",
"1.0.0b5",
"1.0.0b6",
"1.0.0b7",
"1.0.0b8",
"1.0.0b9",
"1.0.1",
"1.0.10",
"1.0.2",
"1.0.3",
"1.0.4",
"1.0.5",
"1.0.6",
"1.0.7",
"1.0.8",
"1.0.9",
"1.1.0",
"1.1.0a1",
"1.1.0a2",
"1.1.0a3",
"1.1.0b1",
"1.1.0b2",
"1.1.0b3",
"1.1.0b4",
"1.1.0rc1",
"1.1.1",
"1.1.2",
"1.1.3",
"1.1.4",
"1.1.5",
"1.1.6",
"1.1.7",
"1.1.8"
]
}
],
"aliases": [
"CVE-2022-36070"
],
"details": "Poetry is a dependency manager for Python. To handle dependencies that come from a Git repository, Poetry executes various commands, e.g. `git config`. These commands are being executed using the executable\u2019s name and not its absolute path. This can lead to the execution of untrusted code due to the way Windows resolves executable names to paths. Unlike Linux-based operating systems, Windows searches for the executable in the current directory first and looks in the paths that are defined in the `PATH` environment variable afterward. This vulnerability can lead to Arbitrary Code Execution, which would lead to the takeover of the system. 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. The victim could also not protect themself by vetting any Git or Poetry config files that might be present in the directory, because the behavior is undocumented. Versions 1.1.9 and 1.2.0b1 contain patches for this issue.",
"id": "PYSEC-2022-43179",
"modified": "2025-04-09T17:27:27.255151+00:00",
"published": "2022-09-07T19:15:08+00:00",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/python-poetry/poetry/security/advisories/GHSA-j4j9-7hg9-97g6"
},
{
"type": "WEB",
"url": "https://github.com/python-poetry/poetry/releases/tag/1.1.9"
},
{
"type": "WEB",
"url": "https://github.com/python-poetry/poetry/releases/tag/1.2.0b1"
}
],
"related": [
"GHSA-j4j9-7hg9-97g6",
"GHSA-j4j9-7hg9-97g6"
],
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.