Some vulnerabilities have been reported in Django, which can be exploited by malicious people to bypass certain security restrictions and conduct script insertion and cross-site request forgery attacks.
1) The cross-site request forgery protection does not properly verify requests with certain "X-Requested-With" headers, which can be exploited to conduct cross-site request forgery attacks by using certain browser plugins and HTTP redirects to send cross-domain HTTP requests with spoofed headers.
2) Input passed via the filename of uploaded files is not properly sanitised within the file field before being used. This can be exploited to insert HTML and script code, which will executed in a user's browser session in context of an affected site if malicious data is viewed.
Successful exploitation requires that a file-storage backend that does not properly sanitise the file name is used (no default file-storage backends are affected).
3) The file-based session storage system does not properly sanitise the key submitted in the session cookie, which can be exploited to conduct directory traversal attacks.
Note: This only affects deployments on systems using path separators other than specified in Python's "os.path.sep" (e.g. Windows systems).
Solution: Update to version 1.1.4 or 1.2.5 or apply patches.
Provided and/or discovered by: The vendor credits:
1) Michael Koziarski
3) Paul McMillan
Original Advisory: http://www.djangoproject.com/weblog/2011/feb/08/security/
Do you have additional information related to this advisory?
Please provide information about patches, mitigating factors, new versions, exploits, faulty patches, links, and other relevant data by posting comments to this Advisory. You can also send this
information to email@example.com
Subject: Django Multiple Vulnerabilities
No posts yet
You must be logged in to post a comment.
Secunia Customer Login
Not a customer already?
Learn more about how our market leading Vulnerability Management solutions can help you manage risk and ensure compliance.