CVE intelligence and bounded remediation
CVE-2022-36070 — Poetry is a dependency manager for Python
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, bec…
- Severity
- High
- CVSS
- 7.3 (3.1)
- Published
- 2022-09-07
- CISA KEV
- Not currently listed
- Ecosystem
- python/pypi
- Weaknesses
- CWE-426
Affected products
- python-poetry / poetry
- python-poetry / poetry / 1.2.0
Matched remediation archetype
Supply-chain, dependency, build, and update integrity
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace affected packages, source archives, build actions, plugins, installers, and updates from declared source to deployed artifact.
- Confirm provenance, signatures or digests, namespace ownership, lockfile resolution, registry configuration, and build-runner trust boundaries.
- Inventory direct, transitive, vendored, generated, and bundled copies across releases and distribution channels.
Remediate safely
- Move to a maintained trusted artifact or remove the dependency; pin immutable identities and verify provenance and integrity before use.
- Regenerate lockfiles and artifacts in a clean isolated build, minimize build credentials and network access, and produce an updated software bill of materials.
- Require reviewed update policy, protected publishing, and reproducible or independently attestable builds where supported.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.