Django
cpe:2.3:a:django_project:django:*:*:*:*:*:*:*
- < 6.0.3
- < 5.2.12
- < 4.2.29
- ~5.0
- ~4.1
- ~3.2
A race condition vulnerability has been identified in Django versions 6.0 prior to 6.0.3, 5.2 prior to 5.2.12, and 4.2 prior to 4.2.29. This vulnerability arises in the file-system storage and file-based cache backends, where concurrent requests can lead to the creation of file system objects with incorrect permissions. In multi-threaded environments, a temporary change in the 'umask' of one thread can inadvertently affect other threads, allowing for exploitation. Unsupported Django versions, such as 5.0.x, 4.1.x, and 3.2.x, may also be vulnerable.
Exploitation of this vulnerability can result in file system objects being created with unintended permissions, potentially leading to unauthorized access or modification of those files.
Users can upgrade to Django versions 6.0.3, 5.2.12, or 4.2.29 to address this vulnerability.
Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.