In Python 3.6 through 3.6.10, 3.7 through 3.7.8, 3.8 through 3.8.4rc1, and 3.9 through 3.9.0b4 on Windows, a Trojan horse python3.dll might
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.5.10, 3.6.12, 3.7.9, 3.8.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In Python 3.6 through 3.6.10, 3.7 through 3.7.8, 3.8 through 3.8.4rc1, and 3.9 through 3.9.0b4 on Windows, a Trojan horse python3.dll might be used in cases where CPython is embedded in a native application. This occurs because python3X.dll may use an invalid search path for python3.dll loading (after Py_SetPath has been used). NOTE: this issue CANNOT occur when using python.exe from a standard (non-embedded) Python installation on Windows.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- libpythonBitnami
From 3.5.0 · fixed in 3.5.10; From 3.6.0 · fixed in 3.6.12; From 3.7.0 · fixed in 3.7.9; From 3.8.0 · fixed in 3.8.4
- pythonBitnami
From 3.5.0 · fixed in 3.5.10; From 3.6.0 · fixed in 3.6.12; From 3.7.0 · fixed in 3.7.9; From 3.8.0 · fixed in 3.8.4
- python-minBitnami
From 3.5.0 · fixed in 3.5.10; From 3.6.0 · fixed in 3.6.12; From 3.7.0 · fixed in 3.7.9; From 3.8.0 · fixed in 3.8.4