Upstream information
Description
The is_safe_url function in utils/http.py in Django 1.4.x before 1.4.6, 1.5.x before 1.5.2, and 1.6 before beta 2 treats a URL's scheme as safe even if it is not HTTP or HTTPS, which might introduce cross-site scripting (XSS) or other vulnerabilities into Django applications that use this function, as demonstrated by "the login view in django.contrib.auth.views" and the javascript: scheme.SUSE information
Overall state of this security issue: Resolved
This issue is currently rated as having moderate severity.
| National Vulnerability Database | |
|---|---|
| Base Score | 4.3 |
| Vector | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | None |
| Integrity Impact | Partial |
| Availability Impact | None |
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
| Product(s) | Source package | State |
|---|---|---|
| Products past their end of life and not receiving proactive updates anymore. | ||
| SUSE Cloud 2.0 | python-django | Already fixed |
| SUSE Cloud 4 | python-django | Already fixed |
| SUSE Cloud 4 Dependencies | python-django | Already fixed |
| Products at an unknown state of their lifecycle. | ||
| SUSE OpenStack Cloud 2.0 | python-django | Already fixed |
| SUSE OpenStack Cloud 4 | python-django | Already fixed |
SUSE Timeline for this CVE
CVE page created: Wed Sep 1 12:32:57 2010CVE page last modified: Tue Jul 2 16:04:46 2024