Gentoo: GLSA-201701-18: Python: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in Python. Please review the CVE identifiers referenced below for details.
Resolution
All Python 2 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-lang/python-2.7.12:2.7"
All Python 3 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-lang/python-3.4.5:3.4"
References
[ 1 ] CVE-2016-0772 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-0772 [ 2 ] CVE-2016-5636 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5636
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201701-18
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.
![Dist Gentoo](/images/distros/dist-gentoo.png)
Synopsis
Multiple vulnerabilities have been found in Python, the worst of which could lead to arbitrary code execution.
Background
Python is an interpreted, interactive, object-oriented programming language.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-lang/python < 3.4.5 *>= 2.7.12 >= 3.4.5
Impact
=====
A remote attacker could entice a user to open a specially crafted index
file using Python's dumbdbm module, possibly resulting in execution of
arbitrary code with the privileges of the process.
A remote attacker could entice a user to process a specially crafted
input stream using Python's zipimporter module, possibly allowing
attackers to cause unspecified impact.
A man in the middle attacker could strip out the STARTTLS command
without generating an exception on the Python SMTP client application,
preventing the establishment of the TLS layer.
Workaround
There is no known workaround at this time.