From the security page (http://www.djangoproject.com/weblog/2007/oct/26/security-fix/): Today we're releasing a fix for a security vulnerability discovered in Django's internationalization framework. The complete details are below, but the executive summary is that you should updated to a fixed version of Django immediately. We are releasing point-releases of all affected Django versions. You can download them at http://www.djangoproject.com/download/. Those tracking trunk development should "svn update" as soon as possible. Please direct any questions about this release to django-users (http://groups.google.com/group/django-users). DESCRIPTION OF VULNERABILITY A per-process cache used by Django's internationalization ("i18n") system to store the results of translation lookups for particular values of the HTTP Accept-Language header used the full value of that header as a key. An attacker could take advantage of this by sending repeated requests with extremely large strings in the Accept-Language header, potentially causing a denial of service by filling available memory. Due to limitations imposed by Web server software on the size of HTTP header fields, combined with reasonable limits on the number of requests which may be handled by a single server process over its lifetime, this vulnerability may be difficult to exploit. Additionally, it is only present when the "USE_I18N" setting in Django is "True" and the i18n middleware component is enabled*. Nonetheless, all users of affected versions of Django are encouraged to update. AFFECTED VERSIONS ... Django 0.96 ... dev-python/django needs to be bumped from 0.96 to 0.96.1 Reproducible: Always
python and Seemant, please advise.
I have an ebuild on the way in (already tested)
in cvs, no keywording or other things necessary (it was never stable)
