The Admin media handler in core/servers/basehttp.py in Django 1.0 and 0.96 does not properly map URL requests to expected "static media files," which allows remote attackers to conduct directory traversal attacks and read arbitrary files via a crafted URL.
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Link | Tags |
---|---|
http://www.openwall.com/lists/oss-security/2009/07/29/2 | mailing list |
http://www.securityfocus.com/bid/35859 | vdb entry |
http://code.djangoproject.com/changeset/11353 | |
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539134 | |
https://www.redhat.com/archives/fedora-package-announce/2009-August/msg00055.html | vendor advisory |
http://secunia.com/advisories/36137 | third party advisory |
http://secunia.com/advisories/36153 | third party advisory |
https://www.redhat.com/archives/fedora-package-announce/2009-August/msg00069.html | vendor advisory |
http://www.djangoproject.com/weblog/2009/jul/28/security/ | patch vendor advisory |