Explore top 10 tips to secure your open-source projects now. Read More

×
Alerts This Week
Warning Icon 1 527
Alerts This Week
Warning Icon 1 527

Gentoo: GLSA-201206-17 Normal: Symlink Attack Risk in Virtualenv

gentoo
Calendar Grey June 22, 2012
Scroller Gentoo
Unsecured temporary files in virtual environments can lead to symbolic link vulnerabilities; it is advisable to update to mitigate potential risks.
An insecure temporary file usage has been reported in virtualenv, possibly allowing symlink attacks.

Summary

The virtualenv.py script in virtualenv does not handle temporary files securely.

Resolution

All virtualenv users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-python/virtualenv-1.5.1"

References

[ 1 ] CVE-2011-4617 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-4617

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201206-17
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: virtualenv: Insecure temporary file usage
Date: June 22, 2012
Bugs: #395285
ID: 201206-17

Synopsis

An insecure temporary file usage has been reported in virtualenv, possibly allowing symlink attacks.

Background

virtualenv is a virtual Python environment builder.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-python/virtualenv < 1.5.1 >= 1.5.1

Impact

===== A local attacker could perform symlink attacks to overwrite arbitrary files with the privileges of the user running the application.

Workaround

There is no known workaround at this time.