CVE-2024-56374: Django has a potential denial-of-service vulnerability in IPv6 validation

Medium CVSS 5.8

OSV id
GHSA-qcgg-j2x8-h9g8
Also known as
BIT-django-2024-56374, CVE-2024-56374, PYSEC-2025-1
Published
Last modified

Affected packages

PackageAffected versionsFixed in
django
PyPI
>= 5.1, < 5.1.5 5.1.5
django
PyPI
>= 5.0, < 5.0.11 5.0.11
django
PyPI
>= 4.2, < 4.2.18 4.2.18
django
PyPI
>= 5.1, < 5.1.5 5.1.5
django
PyPI
>= 5.0, < 5.0.11 5.0.11
django
PyPI
>= 4.2, < 4.2.18 4.2.18

Versions we track that it affects: django 5.0.6, django 4.2.11; django 5.0.6, django 4.2.11; django 5.0.6, django 4.2.11; django 5.0.6, django 4.2.11; django 5.0.6, django 4.2.11; django 5.0.6, django 4.2.11

How to fix it

django (PyPI)

Upgrade django to 5.1.5 or later.

# in requirements.txt: change the line to django==5.1.5
pip install -r requirements.txt
  • If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

django (PyPI)

Upgrade django to 5.0.11 or later.

# in requirements.txt: change the line to django==5.0.11
pip install -r requirements.txt
  • If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

django (PyPI)

Upgrade django to 4.2.18 or later.

# in requirements.txt: change the line to django==4.2.18
pip install -r requirements.txt
  • If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

django (PyPI)

Upgrade django to 5.1.5 or later.

# in requirements.txt: change the line to django==5.1.5
pip install -r requirements.txt
  • If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

django (PyPI)

Upgrade django to 5.0.11 or later.

# in requirements.txt: change the line to django==5.0.11
pip install -r requirements.txt
  • If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

django (PyPI)

Upgrade django to 4.2.18 or later.

# in requirements.txt: change the line to django==4.2.18
pip install -r requirements.txt
  • If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

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

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.