CVE-2014-0483 json
Django data leakage via querystring manipulation in admin
published 12y ago modified 4mo ago also GHSA-rw75-m7gp-92m3 , PYSEC-2014-7 , EUVD-2014-0015
- cvss
- 5.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field parameter in a popup action to an admin change form page, as demonstrated by a /admin/auth/user/?pop=1&t=password URI.
Patch / fix
- pypi django 1.4.14, 1.5.9, 1.6.6, 1.7c3
- python-django Debian 14, Debian 13, Debian 12 1.6.6-1
debian advisories DEBIAN-CVE-2014-0483
- python-django Ubuntu 14.04 LTS 1.6.1-2ubuntu0.4
ubuntu advisories UBUNTU-CVE-2014-0483
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2014-0483 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-0483 updated cvss 3.5
Django: data leakage via querystring manipulation in admin
-
Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) python-django Red Hat OpenStack Platform 4 Django14affected: no fix available
-
Red Hat Subscription Asset Manager Djangoaffected: no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.98% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/django/django/commit/2b31342cdf14fc20e07c43d258f1e7334ad664a6 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | django | <1.4.14 >=1.5, <1.5.9 >=1.6, <1.6.6 >=1.7a1, <1.7c3 |
1.4.14 1.5.9 1.6.6 1.7c3 |
Classification
- Weakness
- Technology feeds
References
-
github.com
/django/django/commit/2b31342cdf14fc20e07c43d258f1e7334ad664a6
web, exploit, patch
-
github.com
/django/django/commit/027bd348642007617518379f8b02546abacaa6e0
web
-
github.com
/django/django/commit/2a446c896e7c814661fb9c4f212b071b2a7fa446
web
-
github.com
/django/django/commit/f7c494f2506250b8cb5923714360a3642ed63e0f
web
-
lists.opensuse.org
/opensuse-updates/2014-09/msg00023.html
vendor-advisory, web
-
debian.org
/security/2014/dsa-3010
vendor-advisory, web, advisory
-
djangoproject.com
/weblog/2014/aug/20/security/
vendor-advisory, article
-
secunia.com
/advisories/61276
third-party-advisory, advisory
-
secunia.com
/advisories/61281
third-party-advisory, advisory
-
secunia.com
/advisories/59782
third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2014-0483
advisory
-
github.com
/django/django
package
-
github.com
/pypa/advisory-database/tree/main/vulns/django/PYSEC-2014-7.yaml
web
-
web.archive.org
/web/20151016194735/http://secunia.com/advisories/61276
web
-
web.archive.org
/web/20151016202523/http://secunia.com/advisories/59782
web
-
web.archive.org
/web/20151023143840/http://secunia.com/advisories/61281
web
-
djangoproject.com
/weblog/2014/aug/20/security
web
-
github.com
/advisories/GHSA-rw75-m7gp-92m3
advisory
Sources
- CVE List CVE-2014-0483
- GitHub Advisory GHSA-rw75-m7gp-92m3
- NVD CVE-2014-0483
- OSV PYSEC-2014-7
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.