First published: Wed Sep 03 2008(Updated: )
Description of problem: The following was reported today to the public (Sept, 2, 2008) via the Django main site: The Django administration application, as a convenience for users whose sessions expire, will attempt to preserve HTTP POST data from an incoming submission while re-authenticating the user, and will -- on successful authentication -- allow the submission to continue without requiring data to be re-entered. Django developer Simon Willison has presented the Django development team with a proof-of-concept cross-site request forgery (CSRF) which exploits this behavior to perform unrequested deletion/modification of data. This exploit has been tested and verified by the Django team, and succeeds regardless of whether Django's bundled CSRF-protection module is active. Version-Release number of selected component (if applicable): Django-0.96.2-1 Extra Info Since I am not aware if the maintainer of the package was given advance notice I'm cc'ing him on this bug.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/0.96.3 | <1 | 1 |
pip/django | >=0.96.0<0.96.3 | 0.96.3 |
pip/django | >=0.95.0<0.95.4 | 0.95.4 |
pip/django | >=0.91.0<0.91.3 | 0.91.3 |
Django | =0.91 | |
Django | =0.96 | |
Django | =0.95 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2008-3909 is classified as a medium-severity vulnerability that may lead to unauthorized data exposure.
To mitigate CVE-2008-3909, it is recommended to upgrade Django to version 0.96.4 or higher.
CVE-2008-3909 affects Django versions from 0.91 up to 0.96.3 inclusive.
Yes, CVE-2008-3909 can be exploited remotely by an attacker to access sensitive data.
CVE-2008-3909 potentially allows attackers to capture and reuse user session data across requests.