django

Vulnerabilities (79)

• CVE-2022-22818Feb 3, 2022
  affected >= 2.2.0, < 2.2.27fixed 2.2.27

  The {% debug %} template tag in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2 does not properly encode the current context. This may lead to XSS.

• CVE-2021-45115Jan 4, 2022
  affected >= 2.2.0, < 2.2.26fixed 2.2.26

  An issue was discovered in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. UserAttributeSimilarityValidator incurred significant overhead in evaluating a submitted password that was artificially large in relation to the comparison values. In a situation where a

• CVE-2021-45116Jan 4, 2022
  affected >= 2.2.0, < 2.2.26fixed 2.2.26

  An issue was discovered in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. Due to leveraging the Django Template Language's variable resolution logic, the dictsort template filter was potentially vulnerable to information disclosure, or an unintended method cal

• CVE-2021-45452Jan 4, 2022
  affected >= 2.2.0, < 2.2.26fixed 2.2.26

  Storage.save in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1 allows directory traversal if crafted filenames are directly passed to it.

• CVE-2021-44420Dec 7, 2021
  affected >= 2.2.0, < 2.2.25fixed 2.2.25

  In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths.

• CVE-2021-35042Jul 2, 2021
  affected >= 3.1.0, < 3.1.13fixed 3.1.13

  Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application.

• CVE-2021-33203Jun 8, 2021
  affected < 2.2.24fixed 2.2.24

  Django before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of arbitrary files. Additionally, if (and only if) the default admindocs te

• CVE-2021-33571Jun 8, 2021
  affected >= 2.2.0, < 2.2.24fixed 2.2.24

  In Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address, and validate_ipv46_address do not prohibit leading zero characters in octal literals. This may allow a bypass of access control that is based on IP addresses. (validate_ipv4

• CVE-2021-32052May 6, 2021
  affected >= 2.2.0, < 2.2.22fixed 2.2.22

  In Django 2.2 before 2.2.22, 3.1 before 3.1.10, and 3.2 before 3.2.2 (with Python 3.9.5+), URLValidator does not prohibit newlines and tabs (unless the URLField form field is used). If an application uses values with newlines in an HTTP response, header injection can occur. Djang

• CVE-2021-31542May 5, 2021
  affected >= 2.2.0, < 2.2.21fixed 2.2.21

  In Django 2.2 before 2.2.21, 3.1 before 3.1.9, and 3.2 before 3.2.1, MultiPartParser, UploadedFile, and FieldFile allowed directory traversal via uploaded files with suitably crafted file names.

• CVE-2021-28658Apr 6, 2021
  affected >= 2.2.0, < 2.2.20fixed 2.2.20

  In Django 2.2 before 2.2.20, 3.0 before 3.0.14, and 3.1 before 3.1.8, MultiPartParser allowed directory traversal via uploaded files with suitably crafted file names. Built-in upload handlers were not affected by this vulnerability.

• CVE-2021-23336Feb 15, 2021
  affected >= 2.2.0, < 2.2.19fixed 2.2.19

  The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9.0 and before 3.9.2 are vulnerable to Web Cache Poisoning via urllib.parse.parse_qsl and urllib.parse.parse_qs by using a vector called parameter cloaking. When

• CVE-2021-3281Feb 2, 2021
  affected >= 2.2.0, < 2.2.18fixed 2.2.18

  In Django 2.2 before 2.2.18, 3.0 before 3.0.12, and 3.1 before 3.1.6, the django.utils.archive.extract method (used by "startapp --template" and "startproject --template") allows directory traversal via an archive with absolute paths or relative paths with dot segments.

• CVE-2020-24584Sep 1, 2020
  affected >= 2.2.0, < 2.2.16fixed 2.2.16

  An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). The intermediate-level directories of the filesystem cache had the system's standard umask rather than 0o077.

• CVE-2020-24583Sep 1, 2020
  affected >= 2.2.0, < 2.2.16fixed 2.2.16

  An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). FILE_UPLOAD_DIRECTORY_PERMISSIONS mode was not applied to intermediate-level directories created in the process of uploading files. It was also not applied to

• CVE-2020-13596Jun 3, 2020
  affected >= 2.2.0, < 2.2.13fixed 2.2.13

  An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. Query parameters generated by the Django admin ForeignKeyRawIdWidget were not properly URL encoded, leading to a possibility of an XSS attack.

• CVE-2020-13254Jun 3, 2020
  affected >= 2.2.0, < 2.2.13fixed 2.2.13

  An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.

• CVE-2020-9402Mar 5, 2020
  affected >= 1.11.0, < 1.11.29fixed 1.11.29

  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 suitably crafted tolerance to GIS functions and aggregates on Oracle, it was possibl

• CVE-2020-7471Feb 3, 2020
  affected >= 1.11.0, < 1.11.28fixed 1.11.28

  Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitabl