pysec-2025-1
Vulnerability from pysec
Published
2025-01-14 19:15
Modified
2025-01-14 21:22
Details

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.)

Impacted products
Name purl
django pkg:pypi/django
Aliases



{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "django",
            purl: "pkg:pypi/django",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "5.1",
                  },
                  {
                     fixed: "5.1.5",
                  },
                  {
                     introduced: "5.0",
                  },
                  {
                     fixed: "5.0.11",
                  },
                  {
                     introduced: "4.2",
                  },
                  {
                     fixed: "4.2.18",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "4.2",
            "4.2.1",
            "4.2.10",
            "4.2.11",
            "4.2.12",
            "4.2.13",
            "4.2.14",
            "4.2.15",
            "4.2.16",
            "4.2.17",
            "4.2.2",
            "4.2.3",
            "4.2.4",
            "4.2.5",
            "4.2.6",
            "4.2.7",
            "4.2.8",
            "4.2.9",
            "5.0",
            "5.0.1",
            "5.0.10",
            "5.0.2",
            "5.0.3",
            "5.0.4",
            "5.0.5",
            "5.0.6",
            "5.0.7",
            "5.0.8",
            "5.0.9",
            "5.1",
            "5.1.1",
            "5.1.2",
            "5.1.3",
            "5.1.4",
         ],
      },
   ],
   aliases: [
      "CVE-2024-56374",
   ],
   details: "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.)",
   id: "PYSEC-2025-1",
   modified: "2025-01-14T21:22:18.665005+00:00",
   published: "2025-01-14T19:15:32+00:00",
   references: [
      {
         type: "ARTICLE",
         url: "https://www.djangoproject.com/weblog/2025/jan/14/security-releases/",
      },
      {
         type: "WEB",
         url: "https://docs.djangoproject.com/en/dev/releases/security/",
      },
      {
         type: "WEB",
         url: "https://groups.google.com/g/django-announce",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2025/01/14/2",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.