First published: Fri Jan 16 2015(Updated: )
Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 allows remote attackers to spoof WSGI headers by using an _ (underscore) character instead of a - (dash) character in an HTTP header, as demonstrated by an X-Auth_User header.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | <=1.4.17 | |
Djangoproject Django | =1.6 | |
Djangoproject Django | =1.6.1 | |
Djangoproject Django | =1.6.2 | |
Djangoproject Django | =1.6.3 | |
Djangoproject Django | =1.6.4 | |
Djangoproject Django | =1.6.5 | |
Djangoproject Django | =1.6.6 | |
Djangoproject Django | =1.6.7 | |
Djangoproject Django | =1.6.8 | |
Djangoproject Django | =1.6.9 | |
Djangoproject Django | =1.7 | |
Djangoproject Django | =1.7.1 | |
Djangoproject Django | =1.7.2 | |
pip/Django | >=1.7<1.7.3 | 1.7.3 |
pip/Django | >=1.6<1.6.10 | 1.6.10 |
pip/django | <1.4.18 | 1.4.18 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-0219 is considered a medium severity vulnerability that allows header spoofing in Django applications.
To fix CVE-2015-0219, upgrade Django to version 1.4.18, 1.6.10, or 1.7.3 or later.
CVE-2015-0219 affects Django versions before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3.
CVE-2015-0219 enables remote attackers to spoof WSGI headers by improperly using underscore characters.
Yes, CVE-2015-0219 can be easily exploited by sending specially crafted HTTP requests to the vulnerable Django application.