CyberRota Analysis
AI-GeneratedDjango versions 5.2 prior to 5.2.17 and 6.0 prior to 6.0.8 are vulnerable to a denial-of-service attack via the `django.utils.translation.check_for_language()` function, which can consume excessive memory when processing numerous long language codes. This vulnerability primarily affects applications that utilize the `django.views.i18n.set_language()` view, potentially leading to service disruptions. Organizations using these Django versions should prioritize applying the necessary updates to mitigate the risk of memory exhaustion attacks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view, which is not routed by default. The consumed memory is bounded, since request data is limited by the `DATA_UPLOAD_MAX_MEMORY_SIZE` setting (default 2.5 MB) and the cache holds a fixed maximum number of entries. 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 Jaeyoung Jang for reporting this issue.