First published: Sun Sep 11 2011(Updated: )
Multiple security flaws have been recently addressed in the v1.3.1 and v1.2.7 versions of the Django Python Web framework (from [1]): 1, Session manipulation, 2, Denial of service attack via URLField, 3, URLField redirection, 4, Host header cache poisoning, 5, Host header and CSRF, 6, Cross-subdomain CSRF attacks, 7, DEBUG pages and sensitive POST data References: [1] <a href="https://www.djangoproject.com/weblog/2011/sep/09/">https://www.djangoproject.com/weblog/2011/sep/09/</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Django | >=1.2.7<=1.3.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-737366 varies, as it includes multiple security flaws affecting session manipulation and denial of service vulnerabilities.
To fix REDHAT-BUG-737366, you should upgrade to Django versions later than 1.3.1 and 1.2.7, where the vulnerabilities have been addressed.
REDHAT-BUG-737366 includes vulnerabilities such as session manipulation, denial of service via URLField, and host header cache poisoning.
REDHAT-BUG-737366 can compromise session integrity, lead to denial of service, and allow for exploitation through malicious URL requests.
Django versions 1.2.7 to 1.3.1 are affected by REDHAT-BUG-737366.