django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
https://hermes.opensuse.org/messages/14700881 | vendor advisory |
http://www.debian.org/security/2011/dsa-2332 | vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=737366 | patch |
http://secunia.com/advisories/46614 | third party advisory |
http://openwall.com/lists/oss-security/2011/09/11/1 | mailing list patch |
https://www.djangoproject.com/weblog/2011/sep/10/127/ | patch |
http://openwall.com/lists/oss-security/2011/09/13/2 | mailing list patch |
https://www.djangoproject.com/weblog/2011/sep/09/ | patch vendor advisory |