Django: Data leakage via admin history log
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
Configuration 4 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| OpenStack Folsom for RHEL 6 | |||
| Django14-0:1.4.4-1.el6ost | cpe:/a:redhat:openstack:2::el6 | RHSA-2013:0670 | 2013-03-21T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-2634-1 | python-django security update |
EUVD |
EUVD-2013-0004 | 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. |
Github GHSA |
GHSA-r7w6-p47g-vj53 | Django Data leakage via admin history log |
Ubuntu USN |
USN-1757-1 | Django vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.9% (1.855% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.