First published: Wed Feb 09 2011(Updated: )
<a href="http://www.djangoproject.com/weblog/2011/feb/08/security/">http://www.djangoproject.com/weblog/2011/feb/08/security/</a> Django's form system includes form fields and widgets for performing file uploads; in rendering these fields, the name of the file currently stored in the field is displayed. In the process of rendering, the filename is displayed without being escaped, as reported by Trac user "e.generalov". In many cases this does not result in a cross-site-scripting vulnerability, as file-storage backends can and are encouraged to (and the default backends provided with Django do) sanitize the supplied filename according to their requirements. However, the risk of a vulnerability appearing in a backend which does not sanitize, or which performs insufficient sanitization, is such that Django will now automatically escape filenames in form rendering.
Affected Software | Affected Version | How to fix |
---|---|---|
Django |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-676359 is considered high due to potential information disclosure risks.
To fix REDHAT-BUG-676359, update your Django installation to the latest version where the vulnerability has been addressed.
REDHAT-BUG-676359 affects the Django framework used for web development.
REDHAT-BUG-676359 includes vulnerabilities related to improper handling of file uploads in Django's form system.
A temporary workaround for REDHAT-BUG-676359 involves modifying the form fields to limit file upload functionalities until an update is applied.