Sign in
Deutsch English Español Polski
Medium

Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS

  • Disclosed: 01.07.2019
  • Updated: 11.10.2026 11:20

An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) django >= 2.1, < 2.1.10, >= 2.2, < 2.2.3, >= 1.11, < 1.11.22 2.1.10, 2.2.3, 1.11.22

References

CVSS score 5.3/10
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness (CWE)
CWE-319
Platform
Python (PyPI)
Package
django
Disclosed
01.07.2019
Updated
11.10.2026 11:20

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2019-10 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-6c7v-2f49-8h26 - CC BY 4.0

Vulnerability history: django

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (162) in the archive
Total entries
162
First → latest
10.2007 08.2026
Without a fix
1
Exploited in attacks
0

Severity breakdown

  • Critical 16
  • High 65
  • Medium 63
  • Low 18

Disclosures per year

earlier: 56

Severity:
  1. Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
    High · 8.8 CVE-2026-15307 < 5.2.17, >= 6.0a1, < 6.0.8 5.2.17, 6.0.8
  2. Django vulnerable to ASGI header spoofing via underscore/hyphen conflation
    High · 7.5 CVE-2026-3902 >= 6.0, < 6.0.4, >= 5.2, < 5.2.13, >= 4.2, < 4.2.30 6.0.4, 5.2.13, 4.2.30
  3. Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit
    High · 7.5 CVE-2026-33034 >= 6.0, < 6.0.4, >= 5.2, < 5.2.13, >= 4.2, < 4.2.30 6.0.4, 5.2.13, 4.2.30
  4. Django vulnerable to Uncontrolled Resource Consumption
    High · 7.5 CVE-2026-25673 >= 6.0, < 6.0.3, >= 5.2, < 5.2.12, >= 4.2, < 4.2.29 6.0.3, 5.2.12, 4.2.29
  5. Django has an SQL Injection issue
    High CVE-2026-1287 >= 6.0a1, < 6.0.2, >= 5.2a1, < 5.2.11, >= 4.2a1, < 4.2.28 6.0.2, 5.2.11, 4.2.28
  6. Django has an SQL Injection issue
    High CVE-2026-1207 >= 6.0a1, < 6.0.2, >= 5.2a1, < 5.2.11, >= 4.2a1, < 4.2.28 6.0.2, 5.2.11, 4.2.28
  7. An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8.
    Critical · 9.1 CVE-2025-64459 >= 4.2, < 4.2.26, >= 5.1, < 5.1.14, >= 5.2, < 5.2.8 4.2.26, 5.1.14, 5.2.8
  8. Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
    High · 7.5 CVE-2025-64458 >= 5.2a1, < 5.2.8, >= 5.0a1, < 5.1.14, < 4.2.26 5.2.8, 5.1.14, 4.2.26
  9. Django vulnerable to SQL injection in column aliases
    High · 7.1 CVE-2025-59681 >= 4.2, < 4.2.25, >= 5.1, < 5.1.13, >= 5.2, < 5.2.7 4.2.25, 5.1.13, 5.2.7
  10. Django is subject to SQL injection through its column aliases
    High · 7.1 CVE-2025-57833 < 4.2.24, >= 5.0a1, < 5.1.12, >= 5.2a1, < 5.2.6 4.2.24, 5.1.12, 5.2.6
  11. Django SQL injection in HasKey(lhs, rhs) on Oracle
    High · 9.8 CVE-2024-53908 >= 5.0.0, < 5.0.10, >= 5.1.0, < 5.1.4, >= 4.2.0, < 4.2.17, >= 5.1, < 5.1.4, >= 5.0, < 5.0.10, >= 4.2, < 4.2.17 5.0.10, 5.1.4, 4.2.17
  12. An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. QuerySet.values() and values_list() methods on models with a JSONField are subject to SQL injection in column aliases via a cr
    Critical · 9.1 CVE-2024-42005 >= 5.0, < 5.0.8, >= 4.2, < 4.2.15 5.0.8, 4.2.15
  13. Django vulnerable to Denial of Service
    High · 7.5 CVE-2024-39614 >= 5.0, < 5.0.7, >= 4.2, < 4.2.14 5.0.7, 4.2.14
  14. Django Path Traversal vulnerability
    High · 7.5 CVE-2024-39330 >= 5.0, < 5.0.7, >= 4.2, < 4.2.14 5.0.7, 4.2.14
  15. Django vulnerable to Denial of Service
    High · 7.5 CVE-2024-38875 >= 4.2, < 4.2.14, >= 5.0, < 5.0.7 4.2.14, 5.0.7
  16. Django denial-of-service attack in the intcomma template filter
    High · 5.9 CVE-2024-24680 >= 3.2, < 3.2.24, >= 4.2, < 4.2.10, >= 5.0, < 5.0.2 3.2.24, 4.2.10, 5.0.2
  17. In Django 3.2 before 3.2.22, 4.1 before 4.1.12, and 4.2 before 4.2.6, the django.utils.text.Truncator chars() and words() methods (when used with html=True) are subject to a potential DoS (denial of s
    High · 5.9 CVE-2023-43665 >= 3.2, < 3.2.22, >= 4.1, < 4.1.12, >= 4.2, < 4.2.6 3.2.22, 4.1.12, 4.2.6
  18. An issue was discovered in Django 3.2 before 3.2.23, 4.1 before 4.1.13, and 4.2 before 4.2.7. The NFKC normalization is slow on Windows. As a consequence, django.contrib.auth.forms.UsernameField is su
    High · 7.5 CVE-2023-46695 >= 3.2, < 3.2.23, >= 4.1, < 4.1.13, >= 4.2, < 4.2.7 3.2.23, 4.1.13, 4.2.7
  19. In Django 3.2 before 3.2.20, 4 before 4.1.10, and 4.2 before 4.2.3, EmailValidator and URLValidator are subject to a potential ReDoS (regular expression denial of service) attack via a very large numb
    High · 7.5 CVE-2023-36053 >= 4.2, < 4.2.3, >= 4.0, < 4.1.10, >= 3.2, < 3.2.20 4.2.3, 4.1.10, 3.2.20
  20. In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using one form field to upload multiple files. This multiple upload has never been suppor
    Critical · 9.8 CVE-2023-31047 >= 3.2, < 3.2.19, >= 4.0, < 4.1.9, >= 4.2, < 4.2.1 3.2.19, 4.1.9, 4.2.1
  21. An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7. Passing certain inputs (e.g., an excessive number of parts) to multipart f
    High · 7.5 CVE-2023-24580 >= 3.2, < 3.2.18, >= 4.0, < 4.0.10, >= 4.1, < 4.1.7 3.2.18, 4.0.10, 4.1.7
  22. In Django 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6, the parsed values of Accept-Language headers are cached in order to avoid repetitive parsing. This leads to a potential denial-of-s
    High · 7.5 CVE-2023-23969 >= 3.2, < 3.2.17, >= 4.0, < 4.0.9, >= 4.1, < 4.1.6 3.2.17, 4.0.9, 4.1.6
  23. In Django 3.2 before 3.2.16, 4.0 before 4.0.8, and 4.1 before 4.1.2, internationalized URLs were subject to a potential denial of service attack via the locale parameter, which is treated as a regular
    High · 7.5 CVE-2022-41323 >= 3.2, < 3.2.16, >= 4.0, < 4.0.8, >= 4.1, < 4.1.2 3.2.16, 4.0.8, 4.1.2
  24. Django vulnerable to Reflected File Download attack
    High · 8.8 CVE-2022-36359 < 3.2.15, >= 4.0, < 4.0.7 3.2.15, 4.0.7
  25. Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection
    Critical · 9.8 CVE-2022-34265 >= 3.2a1, < 3.2.14, >= 4.0a1, < 4.0.6 3.2.14, 4.0.6
  26. Django Arbitrary Code Execution
    High CVE-2007-0404 >= 0.95, < 1.0 1.0
  27. SQL Injection in Django
    Critical · 9.8 CVE-2022-28347 >= 2.2, < 2.2.28, >= 3.2, < 3.2.13, >= 4.0, < 4.0.4 2.2.28, 3.2.13, 4.0.4
  28. SQL Injection in Django
    Critical · 9.8 CVE-2022-28346 >= 2.2, < 2.2.28, >= 3.2, < 3.2.13, >= 4.0, < 4.0.4 2.2.28, 3.2.13, 4.0.4
  29. Infinite Loop in Django
    High · 7.5 CVE-2022-23833 >= 2.2, < 2.2.27, >= 3.2, < 3.2.12, >= 4.0, < 4.0.2 2.2.27, 3.2.12, 4.0.2
  30. Information disclosure in Django
    High · 7.5 CVE-2021-45116 >= 2.2, < 2.2.26, >= 3.2, < 3.2.11, >= 4.0, < 4.0.1 2.2.26, 3.2.11, 4.0.1
  31. Denial-of-service in Django
    High · 7.5 CVE-2021-45115 >= 2.2a1, < 2.2.26, >= 3.2a1, < 3.2.11, >= 4.0a1, < 4.0.1 2.2.26, 3.2.11, 4.0.1
  32. SQL Injection in Django
    Critical · 9.8 CVE-2021-35042 >= 3.2a1, < 3.2.5, >= 3.0a1, < 3.1.13 3.2.5, 3.1.13
  33. Django Access Control Bypass possibly leading to SSRF, RFI, and LFI attacks
    High · 7.5 CVE-2021-33571 >= 2.2a1, < 2.2.24, >= 3.0a1, < 3.1.12, >= 3.2a1, < 3.2.4 2.2.24, 3.1.12, 3.2.4
  34. Path Traversal in Django
    High · 7.5 CVE-2021-31542 >= 2.2, < 2.2.21, >= 3.0, < 3.1.9, >= 3.2, < 3.2.1 2.2.21, 3.1.9, 3.2.1
  35. Django Incorrect Default Permissions
    High · 7.5 CVE-2020-24583 >= 2.2a1, < 2.2.16, >= 3.0a1, < 3.0.10, >= 3.1a1, < 3.1.1 2.2.16, 3.0.10, 3.1.1
  36. Data leakage via cache key collision in Django
    High · 5.9 CVE-2020-13254 >= 2.2, < 2.2.13, >= 3.0, < 3.0.7 2.2.13, 3.0.7
  37. Django 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter in GIS functions and aggregates on Oracle. By passing a suit
    High · 8.8 CVE-2020-9402 >= 1.11, < 1.11.29, >= 2.2, < 2.2.11, >= 3.0, < 3.0.4 1.11.29, 2.2.11, 3.0.4
  38. SQL injection in Django
    Critical · 9.8 CVE-2020-7471 < 1.11.28, >= 2.0, < 2.2.10, >= 3.0, < 3.0.3 1.11.28, 2.2.10, 3.0.3
  39. Django Potential account hijack via password reset form
    Critical · 9.8 CVE-2019-19844 < 1.11.27, >= 2.0, < 2.2.9, >= 3.0, < 3.0.1 1.11.27, 2.2.9, 3.0.1
  40. Django allows unintended model editing
    High · 6.5 CVE-2019-19118 >= 2.1, < 2.1.15, >= 2.2, < 2.2.8 2.1.15, 2.2.8
  41. SQL Injection in Django
    Critical · 9.8 CVE-2019-14234 >= 1.11a1, < 1.11.23, >= 2.1a1, < 2.1.11, >= 2.2a1, < 2.2.4 1.11.23, 2.1.11, 2.2.4
  42. Uncontrolled Recursion in Django
    High · 7.5 CVE-2019-14235 >= 1.11a1, < 1.11.23, >= 2.1a1, < 2.1.11, >= 2.2a1, < 2.2.4 1.11.23, 2.1.11, 2.2.4
  43. Django Denial-of-service in strip_tags()
    High · 7.5 CVE-2019-14233 >= 1.11a1, < 1.11.23, >= 2.1a1, < 2.1.11, >= 2.2a1, < 2.2.4 1.11.23, 2.1.11, 2.2.4
  44. Django Denial-of-service in django.utils.text.Truncator
    High · 7.5 CVE-2019-14232 >= 1.11a1, < 1.11.23, >= 2.1a1, < 2.1.11, >= 2.2a1, < 2.2.4 1.11.23, 2.1.11, 2.2.4
  45. Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS this entry
    Medium · 5.3 CVE-2019-12781 >= 2.1, < 2.1.10, >= 2.2, < 2.2.3, >= 1.11, < 1.11.22 2.1.10, 2.2.3, 1.11.22
  46. Uncontrolled Memory Consumption in Django
    High · 7.5 CVE-2019-6975 >= 1.11, < 1.11.19, >= 2.0, < 2.0.11, >= 2.1, < 2.1.6 1.11.19, 2.0.11, 2.1.6
  47. Improper Input Validation in Django
    High · 6.5 CVE-2019-3498 >= 1.11a1, < 1.11.18, >= 2.0a1, < 2.0.10, >= 2.1a1, < 2.1.5 1.11.18, 2.0.10, 2.1.5
  48. Django vulnerable to information leakage in AuthenticationForm
    High · 7.5 CVE-2018-6188 >= 2.0a1, < 2.0.2, >= 1.11.8, < 1.11.10 2.0.2, 1.11.10
  49. Django before 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3, when settings.DEBUG is True, allow remote attackers to conduct DNS rebinding attacks by leveraging failure to validate
    Critical · 8.1 CVE-2016-9014 < 1.8.16, >= 1.9, < 1.9.11, >= 1.10, < 1.10.3 1.8.16, 1.9.11, 1.10.3
  50. Django 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3 use a hardcoded password for a temporary database user created when running tests with an Oracle database, which makes it easi
    Critical · 9.8 CVE-2016-9013 >= 1.8, < 1.8.16, >= 1.9, < 1.9.11, >= 1.10, < 1.10.3 1.8.16, 1.9.11, 1.10.3
  51. The cookie parsing code in Django before 1.8.15 and 1.9.x before 1.9.10, when used on a site with Google Analytics, allows remote attackers to bypass an intended CSRF protection mechanism by setting a
    High · 7.5 CVE-2016-7401 < 1.8.15, >= 1.9, < 1.9.10 1.8.15, 1.9.10
  52. Django 1.9.x before 1.9.2, when ModelAdmin.save_as is set to True, allows remote authenticated users to bypass intended access restrictions and create ModelAdmin objects via the "Save as New" option w
    High · 5.5 CVE-2016-2048 >= 1.9, < 1.9.2 1.9.2
  53. Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 uses an incorrect regular expression, which allows remote attackers to inject arbitrary headers and conduct HTTP r
    High · 7.5 CVE-2015-5144 < 1.4.21, >= 1.5, < 1.7.9, >= 1.8, < 1.8.3 1.4.21, 1.7.9, 1.8.3
  54. validators.URLValidator in Django 1.8.x before 1.8.3 allows remote attackers to cause a denial of service (CPU consumption) via unspecified vectors.
    High · 7.5 CVE-2015-5145 >= 1.8, < 1.8.3 1.8.3
  55. Django Denial-of-service by filling session store
    High · 7.5 CVE-2015-5143 < 1.4.21, >= 1.5, < 1.7.9, >= 1.8, < 1.8.3 1.4.21, 1.7.9, 1.8.3
  56. The utils.html.strip_tags function in Django 1.6.x before 1.6.11, 1.7.x before 1.7.7, and 1.8.x before 1.8c1, when using certain versions of Python, allows remote attackers to cause a denial of servic
    High · 7.5 CVE-2015-2316 >= 1.6, < 1.6.11, >= 1.7, < 1.7.7, >= 1.8a0, < 1.8c1 1.6.11, 1.7.7, 1.8c1
  57. The django.views.static.serve view in Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 reads files an entire line at a time, which allows remote attackers to cause a denial of service
    High · 7.5 CVE-2015-0221 < 1.4.18, >= 1.5, < 1.6.10, >= 1.7, < 1.7.3 1.4.18, 1.6.10, 1.7.3
  58. ModelMultipleChoiceField in Django 1.6.x before 1.6.10 and 1.7.x before 1.7.3, when show_hidden_initial is set to True, allows remote attackers to cause a denial of service by submitting duplicate val
    High · 7.5 CVE-2015-0222 < 1.4.18, >= 1.5, < 1.6.10, >= 1.7, < 1.7.3 1.4.18, 1.6.10, 1.7.3
  59. The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation
    High · 7.5 CVE-2014-0481 < 1.4.14, >= 1.5, < 1.5.9, >= 1.6, < 1.6.6 1.4.14, 1.5.9, 1.6.6
  60. The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attacker
    High · 7.5 CVE-2014-0480 < 1.4.14, >= 1.5, < 1.5.9, >= 1.6, < 1.6.6 1.4.14, 1.5.9, 1.6.6
  61. The django.util.http.is_safe_url function in Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly validate URLs, which allows remote attackers to conduc
    High · 7.5 CVE-2014-3730 >= 1.4, < 1.4.13, >= 1.5, < 1.5.8, >= 1.6, < 1.6.5, >= 1.7a0, < 1.7b4 1.4.13, 1.5.8, 1.6.5, 1.7b4
  62. Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly include the (1) Vary: Cookie or (2) Cache-Control header in responses, which allows remote attacker
    Critical · 7.4 CVE-2014-1418 >= 1.4, < 1.4.13, >= 1.5, < 1.5.8, >= 1.6, < 1.6.5, >= 1.7a0, < 1.7b4 1.4.13, 1.5.8, 1.6.5, 1.7b4
  63. The django.core.urlresolvers.reverse function in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 allows remote attackers to import and execute arbitrary Pytho
    Critical · 9.8 CVE-2014-0472 < 1.4.11, >= 1.5, < 1.5.6, >= 1.6, < 1.6.3 1.4.11, 1.5.6, 1.6.3
  64. The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 do not properl
    High · 9.8 CVE-2014-0474 < 1.4.11, >= 1.5, < 1.5.6, >= 1.6, < 1.6.3 1.4.11, 1.5.6, 1.6.3
  65. The caching framework in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 reuses a cached CSRF token for all anonymous users, which allows remote attackers to
    High · 7.5 CVE-2014-0473 < 1.4.11, >= 1.5, < 1.5.6, >= 1.6, < 1.6.3 1.4.11, 1.5.6, 1.6.3
  66. The authentication framework (django.contrib.auth) in Django 1.4.x before 1.4.8, 1.5.x before 1.5.4, and 1.6.x before 1.6 beta 4 allows remote attackers to cause a denial of service (CPU consumption)
    High · 7.5 CVE-2013-1443 >= 1.4, < 1.4.8, >= 1.5, < 1.5.4 1.4.8, 1.5.4
  67. Directory traversal vulnerability in Django 1.4.x before 1.4.7, 1.5.x before 1.5.3, and 1.6.x before 1.6 beta 3 allows remote attackers to read arbitrary files via a file path in the ALLOWED_INCLUDE_R
    High · 8.6 CVE-2013-4315 >= 1.4, < 1.4.7, >= 1.5, < 1.5.3 1.4.7, 1.5.3
  68. The django.http.HttpRequest.get_host function in Django 1.3.x before 1.3.4 and 1.4.x before 1.4.2 allows remote attackers to generate and display arbitrary URLs via crafted username and password Host
    High · 7.5 CVE-2012-4520 >= 1.3, < 1.3.4, >= 1.4, < 1.4.2 1.3.4, 1.4.2
  69. The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which
    Critical · 6.1 CVE-2012-3442 < 1.3.2, >= 1.4, < 1.4.1 1.3.2, 1.4.1
  70. The django.forms.ImageField class in the form system in Django before 1.3.2 and 1.4.x before 1.4.1 completely decompresses image data during image validation, which allows remote attackers to cause a
    High · 7.5 CVE-2012-3443 < 1.3.2, >= 1.4, < 1.4.1 1.3.2, 1.4.1
  71. The get_image_dimensions function in the image-handling functionality in Django before 1.3.2 and 1.4.x before 1.4.1 uses a constant chunk size in all attempts to determine dimensions, which allows rem
    High · 7.5 CVE-2012-3444 < 1.3.2, >= 1.4, < 1.4.1 1.3.2, 1.4.1
  72. The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for t
    High · 7.5 CVE-2011-4138 < 1.2.7, >= 1.3, < 1.3.1 1.2.7, 1.3.1
  73. Django before 1.2.7 and 1.3.x before 1.3.1 uses a request's HTTP Host header to construct a full URL in certain circumstances, which allows remote attackers to conduct cache poisoning attacks via a cr
    High · 7.5 CVE-2011-4139 < 1.2.7, >= 1.3, < 1.3.1 1.2.7, 1.3.1
  74. Django Cross-Site Request Forgery vulnerability
    High · 7.5 CVE-2011-4140 <= 1.2.7, >= 1.3, <= 1.3.1 no fix
  75. Denial of service in django
    High · 7.5 CVE-2011-4137 < 1.2.7, >= 1.3, < 1.3.1 1.2.7, 1.3.1
  76. Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site requ
    High · 7.5 CVE-2011-0696 >= 1.1, < 1.1.4, >= 1.2, < 1.2.5 1.1.4, 1.2.5
  77. Directory traversal in Django
    Critical · 9.1 CVE-2011-0698 >= 1.1, < 1.1.4, >= 1.2, < 1.2.5 1.1.4, 1.2.5
  78. The administrative interface in django.contrib.admin in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not properly restrict use of the query string to perform certain objec
    High · 6.5 CVE-2010-4534 < 1.1.3, >= 1.2, < 1.2.4 1.1.3, 1.2.4
  79. Algorithmic complexity vulnerability in the forms library in Django 1.0 before 1.0.4 and 1.1 before 1.1.1 allows remote attackers to cause a denial of service (CPU consumption) via a crafted (1) Email
    High · 7.5 CVE-2009-3695 >= 1.0, < 1.0.4, >= 1.1, < 1.1.1 1.0.4, 1.1.1
  80. The Admin media handler in core/servers/basehttp.py in Django 1.0 and 0.96 does not properly map URL requests to expected "static media files," which allows remote attackers to conduct directory trave
    High · 7.5 CVE-2009-2659 < 1.1 1.1
Show more (2) Showing 80 of 82

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Privacy policy

Free to subscribe. Unsubscribe with one click in any email.