Django vulnerable to XSS on 500 pages
In Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for the technical 500 debug page. Given the right circumstances, this allowed a cross-site scripting attack. This vulnerability shouldn't affect most production sites since you shouldn't run with `DEBUG = True` (which makes this page accessible) in your production settings.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2017-12794US | medium6.1 | — | ||
In Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for the technical 500 debug page. Given the right circumstances… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-9r8w-6x8c-6jr9ADVISORY
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/58e08e80e362db79eb0fd775dc81faad90dca47aWEB
- https://github.com/django/django/commit/e35a0c56086924f331e9422daa266e907a4784ccWEB
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2017-44.yamlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2017-12794ADVISORY
- https://usn.ubuntu.com/3559-1WEB
- https://web.archive.org/web/20170927072701/http://www.securitytracker.com/id/1039264WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan