Potential denial-of-service vulnerability via nested geometry collections
djangoproject Django
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
djangoproject Django
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
An issue was discovered in Django 6.0 before 6.0.9 and 5.2 before 5.2.18. GeoDjango's `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew MacPherson and kimchunbok_ for reporting this issue.
From the CVE record · DSF
GeoDjango can crash when parsing deeply nested GEOMETRYCOLLECTION objects supplied as WKT, WKB, or hex-encoded WKB. This affects GEOSGeometry, spatial field lookups, and GeometryField; an attacker who can supply such geometry input may trigger a denial of service. The input does not specify whether authentication or user interaction is required.
Engineers running Django with GeoDjango should check 5.2 versions before 5.2.18, 6.0 versions before 6.0.9, and affected 6.1 prereleases; earlier unsupported series were not evaluated.