# CVE-2013-0305: Django Data leakage via admin history log

> Remote authenticated administrators can access sensitive object history information in the Django admin interface due to missing permission checks.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-0305, GHSA-r7w6-p47g-vj53, PYSEC-2013-16

## What is CVE-2013-0305?

CVE-2013-0305 is a medium-severity missing authorization vulnerability in Canonical Ubuntu Linux, published on 2 May 2013. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The administrative interface for Django 1.3.x before 1.3.6, 1.4.x before 1.4.4, and 1.5 before release candidate 2 does not check permissions for the history view, which allows remote authenticated administrators to obtain sensitive object history information.

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

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

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 | 1.3.6, 1.4.4 |
| `django` | PyPI | From 1.3 | 1.3.6 |
| `django` | PyPI | From 1.4 | 1.4.4 |
| `Django` | PyPI | From 1.3 | 1.3.6 |
| `Django` | PyPI | From 1.4 | 1.4.4 |

Products: Canonical Ubuntu Linux, Djangoproject Django.

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

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

## Is CVE-2013-0305 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0305 is a medium-severity missing authorization vulnerability in Canonical Ubuntu Linux, published on 2 May 2013. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0305 in the wild and no public exploit code.

Affected packages and fixed versions:
- django (PyPI): affected from 1.3; fixed in 1.3.6, 1.4.4
- django (PyPI): affected from 1.3; fixed in 1.3.6
- django (PyPI): affected from 1.4; fixed in 1.4.4
- Django (PyPI): affected from 1.3; fixed in 1.3.6
- Django (PyPI): affected from 1.4; 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-0305/ (Markdown: https://insights.sbomify.com/CVE-2013-0305/index.md)
```

## Sources

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

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