Virtual environment (venv) activation scripts don't quote paths
A vulnerability has been found in the CPython `venv` module and CLI where path names provided when creating a virtual environment were not quoted properly, allowing the creator to inject commands into virtual environment "activation" scripts (ie "source venv/bin/activate"). This means that attacker-controlled virtual environments are able to run commands when the virtual environment is activated. Virtual environments which are not created by an attacker or which aren't activated before being used (ie "./venv/bin/python") are not affected.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-9287US | high7.8 | — | ||
A vulnerability has been found in the CPython `venv` module and CLI where path names provided when creating a virtual environment were not quoted properly, allowing the creator to… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/python/cpython/commit/633555735a023d3e4d92ba31da35b1205f9ecbd7FIX
- https://github.com/python/cpython/commit/8450b2482586857d689b6658f08de9c8179af7dbFIX
- https://github.com/python/cpython/commit/9286ab3a107ea41bd3f3c3682ce2512692bdded8FIX
- https://github.com/python/cpython/commit/ae961ae94bf19c8f8c7fbea3d1c25cc55ce8ae97FIX
- https://github.com/python/cpython/commit/d48cc82ed25e26b02eb97c6263d95dcaa1e9111bFIX
- https://github.com/python/cpython/commit/e52095a0c1005a87eed2276af7a1f2f66e2b6483FIX
- https://github.com/python/cpython/issues/124651REPORT
- https://github.com/python/cpython/pull/124712FIX
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan