CWE
200
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2013-0305: Infoleak

First published: Fri Feb 22 2013(Updated: )

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.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
debian/python-django
1:1.11.29-1~deb10u1
1:1.11.29-1+deb10u9
2:2.2.28-1~deb11u1
2:2.2.28-1~deb11u2
3:3.2.19-1
3:3.2.19-1+deb12u1
3:3.2.20-1.1
3:3.2.21-1
pip/Django>=1.4<1.4.4
1.4.4
pip/Django>=1.3<1.3.6
1.3.6
djangoproject Django=1.3
djangoproject Django=1.3-alpha1
djangoproject Django=1.3-beta1
djangoproject Django=1.3.1
djangoproject Django=1.3.2
djangoproject Django=1.3.3
djangoproject Django=1.4
djangoproject Django=1.4-alpha
djangoproject Django=1.4-beta
djangoproject Django=1.4.1
djangoproject Django=1.4.2
djangoproject Django=1.5-alpha
djangoproject Django=1.5-beta
Ubuntu Linux=10.04
Ubuntu Linux=11.10
Ubuntu Linux=12.04
Ubuntu Linux=12.10
Ubuntu=10.04
Ubuntu=11.10
Ubuntu=12.04
Ubuntu=12.10

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2013-0305?

    CVE-2013-0305 has a high severity rating due to its potential to expose sensitive object history information to unauthorized users.

  • How do I fix CVE-2013-0305?

    To fix CVE-2013-0305, update Django to version 1.3.6 or higher for the 1.3.x series, or to 1.4.4 or higher for the 1.4.x series.

  • Which Django versions are affected by CVE-2013-0305?

    Django versions 1.3.x before 1.3.6, 1.4.x before 1.4.4, and 1.5 before release candidate 2 are affected by CVE-2013-0305.

  • What type of attack does CVE-2013-0305 allow?

    CVE-2013-0305 allows remote authenticated administrators to access sensitive object history information without proper permission checks.

  • Is CVE-2013-0305 specific to any operating systems?

    CVE-2013-0305 affects Django installations across multiple operating systems that use the vulnerable Django versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203