p PatchFirst

PatchFirst · Latest vulnerabilities

python-django vulnerabilities · Page 3

Vulnerabilities published for python-django in the last 30 days: 3. Listed in the KEV catalogue: 0.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 159

  1. CVE-2024-56374

    Medium · CVSS 5.8EPSS 1.28%Fix available

    CVE-2024-56374

    An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions clean_ipv6_address and is_valid_ipv6_address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)

    • Update to 3:3.2.25-0+deb12u1
    Published Updated
  2. CVE-2024-53907

    High · CVSS 7.5EPSS 1.39%Fix available

    CVE-2024-53907

    An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. The strip_tags() method and striptags template filter are subject to a potential denial-of-service attack via certain inputs containing large sequences of nested incomplete HTML entities.

    • Update to 3:3.2.25-0+deb12u1
    Published Updated
  3. CVE-2024-45231

    Medium · CVSS 5.3EPSS 0.79%Fix available

    CVE-2024-45231

    An issue was discovered in Django v5.1.1, v5.0.9, and v4.2.16. The django.contrib.auth.forms.PasswordResetForm class, when used in a view implementing password reset flows, allows remote attackers to enumerate user e-mail addresses by sending password reset requests and observing the outcome (only when e-mail sending is consistently failing).

    • Update to 3:3.2.25-0+deb12u1
    Published Updated
  4. CVE-2024-41991

    High · CVSS 7.5EPSS 0.95%Fix available

    CVE-2024-41991

    An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The urlize and urlizetrunc template filters, and the AdminURLFieldWidget widget, are subject to a potential denial-of-service attack via certain inputs with a very large number of Unicode characters.

    • Update to 3:3.2.25-0+deb12u1
    Published Updated
  5. CVE-2024-39330

    Medium · CVSS 4.3EPSS 1.01%Fix available

    CVE-2024-39330

    An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. Derived classes of the django.core.files.storage.Storage base class, when they override generate_filename() without replicating the file-path validations from the parent class, potentially allow directory traversal via certain inputs during a save() call. (Built-in Storage sub-classes are unaffected.)

    • Update to 3:3.2.25-0+deb12u1
    Published Updated
  6. CVE-2024-39329

    Medium · CVSS 5.3EPSS 0.89%Fix available

    CVE-2024-39329

    An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. The django.contrib.auth.backends.ModelBackend.authenticate() method allows remote attackers to enumerate users via a timing attack involving login requests for users with an unusable password.

    • Update to 3:3.2.25-0+deb12u1
    Published Updated
  7. CVE-2024-27351

    Medium · CVSS 5.3EPSS 1.85%Fix available

    CVE-2024-27351

    In Django 3.2 before 3.2.25, 4.2 before 4.2.11, and 5.0 before 5.0.3, the django.utils.text.Truncator.words() method (with html=True) and the truncatewords_html template filter are subject to a potential regular expression denial-of-service attack via a crafted string. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232 and CVE-2023-43665.

    • Update to 3:3.2.25-0+deb12u1
    Published Updated
  8. CVE-2023-43665

    High · CVSS 7.5EPSS 1.46%Fix available

    CVE-2023-43665

    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 service) attack via certain inputs with very long, potentially malformed HTML text. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which are thus also vulnerable. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232.

    • Update to 3:3.2.25-0+deb12u1
    Published Updated
  9. CVE-2023-31047

    Critical · CVSS 9.8EPSS 1.39%Fix available

    CVE-2023-31047

    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 supported by forms.FileField or forms.ImageField (only the last uploaded file was validated). However, Django's "Uploading multiple files" documentation suggested otherwise.

    • Update to 3:3.2.19-1
    Published Updated
  10. CVE-2023-24580

    High · CVSS 7.5EPSS 62.58%Fix available

    CVE-2023-24580

    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 forms could result in too many open files or memory exhaustion, and provided a potential vector for a denial-of-service attack.

    • Update to 3:3.2.18-1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →