CPython: Improper Neutralization of Special Elements used in a Command
CVE-2024-9287 is a high-severity improper neutralization of special elements used in a command vulnerability in CPython from Python Software Foundation, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 3.9.21, 3.10.16, 3.11.11 as the first without the flaw, so updating CPython to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.65% chance of exploitation within 30 days, higher than 52% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update CPython to 3.9.21 or 3.10.16 or 3.11.11 or 3.12.8, whichever matches your release line, or a later version.
- Update Python to 3.9.21 or 3.10.16 or 3.11.11 or 3.12.8, whichever matches your release line, or a later version.
- Read the advisory on mail.python.org for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Python Software Foundation | CPython | before 3.9.21; 3.10.0 up to, but not including, 3.10.16; 3.11.0 up to, but not including, 3.11.11; 3.12.0 up to, but not including, 3.12.8; 3.13.0 up to, but not including, 3.13.1; 3.14.0a1 up to, but not including, 3.14.0a2 | 3.9.21, 3.10.16, 3.11.11, 3.12.8, 3.13.1, 3.14.0a2 |
| Python | Python | before 3.9.21; 3.10.0 up to, but not including, 3.10.16; 3.11.0 up to, but not including, 3.11.11; 3.12.0 up to, but not including, 3.12.8; 3.13.0 up to, but not including, 3.13.1; 3.14.0 | 3.9.21, 3.10.16, 3.11.11, 3.12.8, 3.13.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 5.3 | Medium | CNA (python.org) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in a Command
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- If possible, ensure that all external commands called from the program are statically created.
- Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
More Improper Neutralization of Special Elements used in a Command vulnerabilities (CWE-77)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/python/cpython/commit/633555735a023d3e4d92ba31da35b1205f9ecbd7
- github.com/python/cpython/commit/8450b2482586857d689b6658f08de9c8179af7db
- github.com/python/cpython/commit/9286ab3a107ea41bd3f3c3682ce2512692bdded8
- github.com/python/cpython/commit/ae961ae94bf19c8f8c7fbea3d1c25cc55ce8ae97
- github.com/python/cpython/commit/d48cc82ed25e26b02eb97c6263d95dcaa1e9111b
- github.com/python/cpython/commit/e52095a0c1005a87eed2276af7a1f2f66e2b6483
- github.com/python/cpython/pull/124712Issue Tracking
Other references
Other vulnerabilities in CPython
- 8.2 High severity
- 9.4 Critical severity
- 7.6 High severity
- 9.2 Critical severity
- 8.4 High severity
- 7.5 High severity
Recent Improper Neutralization of Special Elements used in a Command vulnerabilities
- 9.8 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
- 7.2 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.