# CVE-2013-1665: XML External Entity (XXE) in Django

> Remote attackers can read arbitrary files via XML External Entity attacks in Python XML libraries, affecting applications like OpenStack and Django.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Apr 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-1665, GHSA-x64m-686f-fmm3, PYSEC-2026-802

## What is CVE-2013-1665?

CVE-2013-1665 is a medium-severity vulnerability in n/a, published on 3 Apr 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The XML libraries for Python 3.4, 3.3, 3.2, 3.1, 2.7, and 2.6, as used in OpenStack Keystone Essex and Folsom, Django, and possibly other products allow remote attackers to read arbitrary files via an XML external entity declaration in conjunction with an entity reference, aka an XML External Entity (XXE) attack.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-1665?

5 open source packages ship an affected version, including django and Django. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `django` | PyPI | From 1.3.0 | 1.3.6, 1.4.4 |
| `django` | PyPI | From 1.3.0 | 1.3.6 |
| `django` | PyPI | From 1.4.0 | 1.4.4 |
| `Django` | PyPI | From 1.3.0 | 1.3.6 |
| `Django` | PyPI | From 1.4.0 | 1.4.4 |

Products: Openstack Folsom, Openstack Keystone Essex.

## How do I fix CVE-2013-1665?

Upgrade django to a fixed version for your release line: 1.3.6 or 1.4.4.

## Is CVE-2013-1665 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2161](https://insights.sbomify.com/CVE-2013-2161/): OpenStack Swift Unchecked user input in XML responses (high 7.5)
- [CVE-2013-4497](https://insights.sbomify.com/CVE-2013-4497/): OpenStack Compute Nova Improper Access Control (medium 6.4)
- [CVE-2012-3447](https://insights.sbomify.com/CVE-2012-3447/): Arbitrary file overwrite in OpenStack Nova (medium 4.9)
- [CVE-2012-5625](https://insights.sbomify.com/CVE-2012-5625/): OpenStack Nova Information leak in libvirt LVM-backed instances (medium 4.3)
- [CVE-2013-4155](https://insights.sbomify.com/CVE-2013-4155/): OpenStack Swift allows authenticated users to cause a denial of service (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1665 and fix it if it is affected.

What it is: CVE-2013-1665 is a medium-severity vulnerability in n/a, published on 3 Apr 2013. 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-2013-1665 in the wild and no public exploit code.

Affected packages and fixed versions:
- django (PyPI): affected from 1.3.0; fixed in 1.3.6, 1.4.4
- django (PyPI): affected from 1.3.0; fixed in 1.3.6
- django (PyPI): affected from 1.4.0; fixed in 1.4.4
- Django (PyPI): affected from 1.3.0; fixed in 1.3.6
- Django (PyPI): affected from 1.4.0; fixed in 1.4.4

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-2013-1665/ (Markdown: https://insights.sbomify.com/CVE-2013-1665/index.md)
```

## Sources

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

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