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.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | =1.1.2 | |
Djangoproject Django | =1.1 | |
Djangoproject Django | =1.1.3 | |
Djangoproject Django | =1.1.0 | |
Djangoproject Django | =1.2.1 | |
Djangoproject Django | =1.2.4 | |
Djangoproject Django | =1.2.3 | |
Djangoproject Django | =1.2 | |
Djangoproject Django | =1.2.2 | |
pip/Django | >=1.2<1.2.5 | 1.2.5 |
pip/Django | >=1.1<1.1.4 | 1.1.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.