Forum Thread: Django "i18n" Denial of Service Vulnerability

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:

See the original Secunia advisory:
Django "i18n" Denial of Service Vulnerability

Secunia Django "i18n" Denial of Service Vulnerability
Secunia Official 16th Jul, 2010 22:57
Ranking: 0
Posts: 0
User Since: -
System Score: -
Location: Copenhagen, DK
A vulnerability has been reported in Django, which potentially can be exploited by malicious people to cause a DoS (Denial of Service).

The vulnerability is caused due to the Django internationalization system ("i18n") incorrectly processing HTTP headers. This can be exploited to allocate large amounts of memory by sending specially crafted HTTP "Accept-Language" requests.

Successful exploitation requires that the "USE_I18N" option and the "i18n" middleware component are enabled.

The vulnerability is reported in version 0.91, 0.95, 0.95.1 and 0.96.


RE: Django "i18n" Denial of Service Vulnerability
This reply has been minimised due to a negative Relevancy Score.
thedillpickl RE: Django "i18n" Denial of Service Vulnerability
Contributor 17th Jul, 2010 00:16
Score: 376
Posts: 872
User Since: 3rd May 2009
System Score: N/A
Location: US
Hi pinkgranite;

Secunia is explaining the vulnerability, not seeking thoughts or opinions.

If, however, someone has working knowledge of the vulnerability and has pertinent information regarding it, then it is appropriate to post here. Otherwise it might be better to post opinions in the "Open Discussions" part of the forum.

Hope this tip helps!



XP Home
Chrome, Firefox, IE8
consilio et animis
Was this reply relevant?