CVE-2011-4617: Medium severity virtualenv vulnerability
Published Dec 31, 2011
·Updated
virtualenv.py in virtualenv before 1.5 allows local users to overwrite arbitrary files via a symlink attack on a certain file in /tmp/.
Affected Software
28 affected componentsFixes available
pip/virtualenv<1.5
1.5
Python Virtualenv=1.3.4
Python Virtualenv<=1.4.9
Python Virtualenv=1.4.3
Python Virtualenv=0.9.1
Python Virtualenv=1.2
Python Virtualenv=0.8.3
Python Virtualenv=0.8.1
Python Virtualenv=0.8.4
Python Virtualenv=1.3.2
Python Virtualenv=1.3.3
Python Virtualenv=0.8.2
Python Virtualenv=1.4.6
Python Virtualenv=1.4.2
Python Virtualenv=1.4.5
Python Virtualenv=1.4.4
Python Virtualenv=0.9
Python Virtualenv=1.1
Python Virtualenv=0.9.2
Python Virtualenv=1.4.8
Python Virtualenv=1.1.1
Python Virtualenv=1.4.7
Python Virtualenv=1.4
Python Virtualenv=1.3.1
Python Virtualenv=1.3
Python Virtualenv=1.4.1
Python Virtualenv=1.0
Python Virtualenv=0.8
Event History
Dec 31, 2011
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
May 17, 2022
Advisory Published
via GitHub·05:35 AM
Frequently Asked Questions
1
What is the severity of CVE-2011-4617?
The CVE-2011-4617 vulnerability is considered to have a moderate severity, as it allows local users to overwrite arbitrary files.
2
How do I fix CVE-2011-4617?
To fix CVE-2011-4617, you should upgrade to virtualenv version 1.5 or later.
3
Which versions of virtualenv are affected by CVE-2011-4617?
CVE-2011-4617 affects virtualenv versions prior to 1.5, including versions 1.4.9 and earlier.
4
Is CVE-2011-4617 a remote or local vulnerability?
CVE-2011-4617 is a local vulnerability that requires access to the system to exploit.
5
What impact does CVE-2011-4617 have on system security?
CVE-2011-4617 can lead to unauthorized file modifications, potentially compromising the integrity of the system.