Django vulnerable to Denial of Service via i18n middleware component
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
The internationalization (i18n) framework in Django 0.91, 0.95, 0.95.1, and 0.96, and as used in other products such as PyLucid, when the USE_I18N option and the i18n component are enabled, allows remote attackers to cause a denial of service (memory consumption) via many HTTP requests with large Accept-Language headers.
From the CVE record · mitre
Django’s internationalization framework is vulnerable when USE_I18N and the i18n component are enabled. A remote attacker can cause memory exhaustion by sending many HTTP requests with large Accept-Language headers; the description does not specify an authentication or user-interaction requirement.
Teams running affected PyPI django versions, including 0.91, 0.95, 0.95.1, and 0.96, should check their deployments.