December 2, 2019
Django is prone to a privilege-escalation vulnerability. A remote attacker can exploit this issue to gain elevated privileges and perform unauthorized actions on an affected system. Django versions prior to 2.2.8 and 2.1.15 are vulnerable.
- Djangoproject Django 2.1
- Djangoproject Django 2.1.1
- Djangoproject Django 2.1.10
- Djangoproject Django 2.1.11
- Djangoproject Django 2.1.12
- Djangoproject Django 2.1.13
- Djangoproject Django 2.1.14
- Djangoproject Django 2.1.2
- Djangoproject Django 2.1.3
- Djangoproject Django 2.1.4
- Djangoproject Django 2.1.5
- Djangoproject Django 2.1.6
- Djangoproject Django 2.1.7
- Djangoproject Django 2.1.8
- Djangoproject Django 2.1.9
- Djangoproject Django 2.2
- Djangoproject Django 2.2.1
- Djangoproject Django 2.2.2
- Djangoproject Django 2.2.3
- Djangoproject Django 2.2.4
- Djangoproject Django 2.2.5
- Djangoproject Django 2.2.6
- Djangoproject Django 2.2.7
Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of successful exploits.
Run all software as a nonprivileged user with minimal access rights.
When possible, run client software as regular user accounts with limited access to system resources. This may limit the immediate consequences of client-side vulnerabilities.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of suspicious or anomalous activity. This may help detect malicious actions that an attacker may take after successfully exploiting vulnerabilities in applications. Review logs regularly.
Implement multiple redundant layers of security.
Various memory-protection schemes (such as nonexecutable and randomly mapped memory segments) may hinder an attacker's ability to exploit this vulnerability to execute arbitrary code.
Updates are available. Please see the references or vendor advisory for more information.
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.