Quick answers
- Is CVE-2010-4534 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2010-4534 being exploited in the wild.
- How severe is CVE-2010-4534?
- Medium severity, with a CVSS score of 6.5, published 23 July 2018.
- Which products and versions are affected?
- Django (PyPI) ECOSYSTEM:introduced=0,fixed=1.1.3, ECOSYSTEM:introduced=0,fixed=1.1.3,introduced=1.2,fixed=1.2.4, ECOSYSTEM:introduced=0,fixed=1.1.3|ECOSYSTEM:introduced=1.2,fixed=1.2.4.
- Is there a fix for CVE-2010-4534?
- Yes. Django (PyPI): upgrade to 1.1.3, 1.2.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2010-4534 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2010-4534?
- Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Django (PyPI): upgrade to 1.1.3, 1.2.4 or later
pip install "Django>=1.2.4"
Technical details
The vulnerability exists in the 'django.contrib.admin' component due to improper validation of query string parameters used for object filtering. An authenticated remote attacker can bypass intended access controls by appending specialized parameters (e.g., using '__regex' or '__contains' filters) to administrative URLs. By observing the presence or absence of results in the admin interface across multiple requests, an attacker can perform a side-channel attack to reconstruct sensitive fields, such as password hashes or other private model data. This issue is addressed in Django versions 1.1.3 and 1.2.4.
Affected products
- Django Django < 1.1.3, >= 1.2, < 1.2.4, 1.3.x < 1.3 beta 1
Identifiers
- CVE-2010-4534
- GHSA-fwr5-q9rx-294f
- PYSEC-2011-28
- PYSEC-2011-8
Timeline
- 2010-12-22: disclosed: Initial security advisory by Django project
- 2011-01-10: advisory: NVD publication date
- 2018-07-23: advisory: GitHub Advisory Database publication