CVE-2012-5379: High severity activestate activepython vulnerability
DISPUTED Untrusted search path vulnerability in the installation functionality in ActivePython 3.2.2.3, when installed in the top-level C:\ directory, might allow local users to gain privileges via a Trojan horse DLL in the C:\Python27 or C:\Python27\Scripts directory, which may be added to the PATH system environment variable by an administrator, as demonstrated by a Trojan horse wlbsctrl.dll file used by the "IKE and AuthIP IPsec Keying Modules" system service in Windows Vista SP1, Windows Server 2008 SP2, Windows 7 SP1, and Windows 8 Release Preview. NOTE: CVE disputes this issue because the unsafe PATH is established only by a separate administrative action that is not a default part of the ActivePython installation.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2012-5379?
CVE-2012-5379 is considered a moderate severity vulnerability due to its potential to allow local privilege escalation.
How do I fix CVE-2012-5379?
To fix CVE-2012-5379, avoid installing ActivePython in the top-level C:\ directory and ensure that untrusted directories are not included in the system PATH.
Who is affected by CVE-2012-5379?
CVE-2012-5379 affects users of ActivePython version 3.2.2.3 installed in insecure locations.
What causes CVE-2012-5379?
CVE-2012-5379 is caused by an untrusted search path vulnerability in the installation functionality of ActivePython.
Can a Trojan horse DLL exploit CVE-2012-5379?
Yes, a Trojan horse DLL placed in the C:\Python27 or C:\Python27\Scripts directory can exploit CVE-2012-5379 to gain local privileges.