# CVE-2007-5712: Django vulnerable to Denial of Service via i18n middleware component

> Remote attackers can cause denial of service via memory consumption using large Accept-Language headers when internationalization is enabled.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5712, GHSA-9v8h-57gv-qch6, PYSEC-2007-1

## What is CVE-2007-5712?

CVE-2007-5712 is a low-severity denial of service vulnerability in n/a, published on 30 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-399

## Which versions are affected by CVE-2007-5712?

7 open source packages ship an affected version, including django and Django. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `django` | PyPI | All versions | 1.1 |
| `django` | PyPI | From 0.91.0 | 0.91.1 |
| `django` | PyPI | From 0.95 | 0.95.2 |
| `django` | PyPI | From 0.96.0 | 0.96.1 |
| `Django` | PyPI | From 0.91.0 | 0.91.1 |
| `Django` | PyPI | From 0.95 | 0.95.2 |
| `Django` | PyPI | From 0.96.0 | 0.96.1 |

Products: Django Project Django.

## How do I fix CVE-2007-5712?

Upgrade django to a fixed version for your release line: 1.1, 0.91.1, 0.95.2 or 0.96.1.

## Is CVE-2007-5712 being exploited?

There is no known exploitation of CVE-2007-5712 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-0404](https://insights.sbomify.com/CVE-2007-0404/): Django Arbitrary Code Execution (high 7.5)
- [CVE-2007-5828](https://insights.sbomify.com/CVE-2007-5828/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2007-0405](https://insights.sbomify.com/CVE-2007-0405/): Django Improper Access Control (medium 6.5)
- [CVE-2009-2659](https://insights.sbomify.com/CVE-2009-2659/): Django Admin Media Handler Vulnerable to Directory Traversal (medium 5.0)
- [CVE-2008-2302](https://insights.sbomify.com/CVE-2008-2302/): Django Cross-site scripting (XSS) vulnerability (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5712 and fix it if it is affected.

What it is: CVE-2007-5712 is a low-severity denial of service vulnerability in n/a, published on 30 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-5712 in the wild and no public exploit code.

Affected packages and fixed versions:
- django (PyPI): affected all versions; fixed in 1.1
- django (PyPI): affected from 0.91.0; fixed in 0.91.1
- django (PyPI): affected from 0.95; fixed in 0.95.2
- django (PyPI): affected from 0.96.0; fixed in 0.96.1
- Django (PyPI): affected from 0.91.0; fixed in 0.91.1
- Django (PyPI): affected from 0.95; fixed in 0.95.2
- Django (PyPI): affected from 0.96.0; fixed in 0.96.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2007-5712/ (Markdown: https://insights.sbomify.com/CVE-2007-5712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-5712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-5712
- OSV: https://osv.dev/vulnerability/CVE-2007-5712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-5712/
Summaries are generated and may contain mistakes; the official description above is the record.