Bug 913041 (CVE-2013-0305) - CVE-2013-0305 Django: Data leakage via admin history log
Summary: CVE-2013-0305 Django: Data leakage via admin history log
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-0305
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 913043 913044 913045 913048 913050 913054 1005404
Blocks: 916886
TreeView+ depends on / blocked
 
Reported: 2013-02-20 09:29 UTC by Kurt Seifried
Modified: 2019-09-29 13:01 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-07 18:59:08 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0670 0 normal SHIPPED_LIVE Moderate: Django security update 2013-03-21 22:12:01 UTC

Description Kurt Seifried 2013-02-20 09:29:08 UTC 
James Bennett of Django reports:

Django's bundled administrative interface keeps a log of actions taken, preserving the history of any object which is exposed through the admin interface. This history view does not perform any permission checks beyond confirming that the user has access to the administrative interface; as such, any user with admin access can view the history of any object accessible in the admin interface, and see summaries of each change made to an object.

To remedy this, the admin history view for an object will now perform the same permission checks as other admin views for the same object.

External reference:
https://www.djangoproject.com/weblog/2013/feb/19/security/
Comment 1 Kurt Seifried 2013-02-20 09:33:35 UTC 
Created Django tracking bugs for this issue

Affects: epel-5 [bug 913043]
Comment 2 Kurt Seifried 2013-02-20 09:36:04 UTC 
Created Django14 tracking bugs for this issue

Affects: epel-6 [bug 913045]
Comment 3 Kurt Seifried 2013-02-20 09:36:08 UTC 
Created Django tracking bugs for this issue

Affects: epel-6 [bug 913044]
Comment 4 Kurt Seifried 2013-02-20 09:38:22 UTC 
Created Django tracking bugs for this issue

Affects: fedora-17 [bug 913048]
Comment 8 Fedora Update System 2013-03-11 19:32:45 UTC 
Django14-1.4.5-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2013-03-12 08:49:44 UTC 
python-django-1.4.5-2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 10 Fedora Update System 2013-03-12 08:53:50 UTC 
Django-1.4.5-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 11 errata-xmlrpc 2013-03-21 18:12:46 UTC 
This issue has been addressed in following products:

  OpenStack Folsom for RHEL 6

Via RHSA-2013:0670 https://rhn.redhat.com/errata/RHSA-2013-0670.html
Note You need to log in before you can comment on or make changes to this bug.