Tarek Nakkouch

Name of the Vulnerable Software and Affected Versions Django versions 6.0 through 6.0.3, 5.2 through 5.2.12, and 4.2 through 4.2.29 Description The `ASGIRequest` component allows a remote attacker to spoof headers due to an ambiguous mapping of header variants (with hyphens or with underscores) to a single version with underscores. Recommendations Update to Django version 6.0.4 or later. Update to Django version 5.2.13 or later. Update to Django version 4.2.30 or later.

**Name of the Vulnerable Software and Affected Versions** Django versions 4.2 before 4.2.29 Django versions 5.2 before 5.2.12 Django versions 6.0 before 6.0.3 Django versions 3.2.x and earlier Django versions 4.1.x and earlier Django versions 5.0.x and earlier **Description** A race condition exists in Django's file-system storage and file-based cache backends. This condition can lead to the creation of file system objects with incorrect permissions when concurrent requests are processed in multi-threaded environments. Specifically, a temporary `umask` change made by one thread can affect other threads, resulting in unintended file permissions. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) may also be affected. **Recommendations** Update Django to version 4.2.29 or later. Update Django to version 5.2.12 or later. Update Django to version 6.0.3 or later. Update Django to a version later than 3.2.x. Update Django to a version later than 4.1.x. Update Django to a version later than 5.0.x.

**Name of the Vulnerable Software and Affected Versions** GitHub Copilot and Visual Studio (affected versions not specified) **Description** The software contains a command injection issue due to improper neutralization of special elements used in commands. A successful exploit could allow an authorized attacker to elevate privileges over a network. The issue relates to a failure to sanitize data at the management level. Exploitation may allow a remote attacker to elevate their privileges. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Django versions prior to 6.0.2 Django versions prior to 5.2.11 Django versions prior to 4.2.28 **Description** A flaw in the GeoDjango `RasterField` implementation, specifically when using a PostGIS backend, allows remote attackers to perform SQL injection. The issue occurs because the software fails to properly parameterize the band index during raster lookup processing, allowing user-supplied input to be concatenated directly into SQL queries. This can lead to unauthorized information disclosure, data alteration, denial of service, or potential remote code execution on database hosts. Real-world incidents indicate that this issue has been actively exploited in targeted attacks against mapping platforms, location services, and geospatial analytics applications. The vulnerability is triggered via the `band` index parameter during raster lookups. **Recommendations** Update Django to version 6.0.2. Update Django to version 5.2.11. Update Django to version 4.2.28. Restrict access to raster endpoints to minimize the risk of exploitation. Enforce strict input validation on the `band` index parameter. Deploy WAF rules to filter common SQL injection patterns.