Allocation of Resources Without Limits or ThrottlingDjango is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the _parse method of MultiPartParser in django/http/multipartparser.py. An attacker can exhaust server memory by sending a multipart upload with Content-Transfer-Encoding: base64 whose data does not align to a 4-byte boundary, so the parser reads the entire upload into memory rather than honoring FILE_UPLOAD_MAX_MEMORY_SIZE. The impact is denial of service through memory exhaustion, reachable on any endpoint that accepts multipart file uploads.
How to fix Allocation of Resources Without Limits or Throttling? Upgrade Django to version 5.2.19, 6.0.10, 6.1.3 or higher.
| [5.2a1,5.2.19)[6.0a1,6.0.10)[6.1a1,6.1.3) |
Improper Output Neutralization for LogsDjango is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
Affected versions of this package are vulnerable to Improper Output Neutralization for Logs in the deserialize method of BaseGeometryWidget in django/contrib/gis/forms/widgets.py. An attacker can write unescaped control characters such as newlines or ANSI escape sequences into application logs by submitting an invalid value to a GeometryField, which is logged verbatim when geometry construction fails. The impact depends on how those logs are later processed or viewed, for example in a terminal or an external log aggregator.
How to fix Improper Output Neutralization for Logs? Upgrade Django to version 5.2.19, 6.0.10, 6.1.3 or higher.
| [5.2a1,5.2.19)[6.0a1,6.0.10)[6.1a1,6.1.3) |
Use of Cache Containing Sensitive InformationDjango is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information in the _generate_cache_key function in django/utils/cache.py. An attacker can receive another user's cached response by sending a request that omits a header named in the response Vary header, because an absent header and a header present with an empty value are assigned the same cache key. This affects applications using UpdateCacheMiddleware or cache_page() whose cached responses vary on a request header.
How to fix Use of Cache Containing Sensitive Information? Upgrade Django to version 5.2.19, 6.0.10, 6.1.3 or higher.
| [5.2a1,5.2.19)[6.0a1,6.0.10)[6.1a1,6.1.3) |
Server-side Request Forgery (SSRF)Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in GeoDjango's GeoJSON handling, reached through spatial-field lookups, the GeometryField form field, and the GEOSGeometry constructor. An attacker can make the server issue outbound network requests as the Django process user or read local files by submitting a GeoJSON geometry whose crs member references an external URL, which GDAL resolves. Exploitation requires a path that instantiates a geometry from untrusted input, and the DataSource and LayerMapping loaders are out of scope because they are intended for trusted data.
How to fix Server-side Request Forgery (SSRF)? Upgrade Django to version 5.2.19, 6.0.10, 6.1.3 or higher.
| [5.2a1,5.2.19)[6.0a1,6.0.10)[6.1a1,6.1.3) |
Server-side Request Forgery (SSRF)Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the SpatialReference class in django/contrib/gis/gdal/srs.py, reached through GEOSGeometry.transform(), OGRGeometry.transform(), GDALRaster.transform(), and the srs and srid setters of OGRGeometry and GDALRaster. An attacker can make the server issue outbound file and network requests, and by observing those requests infer local file contents, by supplying an untrusted spatial-reference string that GDAL's OSRSetFromUserInput resolves as an external reference. Exploitation requires an application that passes untrusted input into GeoDjango's spatial-reference handling, and the external resolution is a default of the underlying GDAL library.
How to fix Server-side Request Forgery (SSRF)? Upgrade Django to version 5.2.19, 6.0.10, 6.1.3 or higher.
| [5.2a1,5.2.19)[6.0a1,6.0.10)[6.1a1,6.1.3) |