Gentoo: GLSA-201510-06: Django: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been found in Django:
* Session backends create a new record anytime request.session was
accessed (CVE-2015-5143)
* Built-in validators in Django do not properly sanitize input
(CVE-2015-5144)
* URL validation included a regular expression that was extremely slow
(CVE-2015-5145)
Resolution
All Django 1.8 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-python/django-1.8.3"
All Django 1.7 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-python/django-1.7.9"
All Django 1.4 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-python/django-1.4.21"
References
[ 1 ] CVE-2015-5143 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-5143 [ 2 ] CVE-2015-5144 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-5144 [ 3 ] CVE-2015-5145 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-5145
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201510-06
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 Django, the worst of which may allow a remote attacker to cause Denial of Service.
Background
Django is a Python-based web framework.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-python/django < 1.8.3 >= 1.8.3 *>= 1.7.9 *>= 1.4.21
Impact
===== A remote attacker may be able cause a Denial of Service condition, inject arbitrary headers, and conduct HTTP response splitting attacks.
Workaround
There is no known workaround at this time.