First published: Wed Jun 03 2020(Updated: )
An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | >=2.2<2.2.13 | |
Djangoproject Django | >=3.0<3.0.7 | |
Canonical Ubuntu Linux | =14.04 | |
Canonical Ubuntu Linux | =16.04 | |
Canonical Ubuntu Linux | =18.04 | |
Canonical Ubuntu Linux | =19.10 | |
Canonical Ubuntu Linux | =20.04 | |
Fedoraproject Fedora | =32 | |
Netapp Sra Plugin | ||
Netapp Steelstore Cloud Integrated Storage | ||
Debian Debian Linux | =8.0 | |
Debian Debian Linux | =9.0 | |
Debian Debian Linux | =10.0 | |
Oracle ZFS Storage Appliance Kit | =8.8 | |
pip/Django | >=3.0<3.0.7 | 3.0.7 |
pip/Django | >=2.2<2.2.13 | 2.2.13 |
debian/python-django | 2:2.2.28-1~deb11u2 3:3.2.19-1+deb12u1 3:4.2.16-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-13254 is a vulnerability in Django versions 2.2 before 2.2.13 and 3.0 before 3.0.7 that can result in key collision and potential data leakage.
CVE-2020-13254 has a severity rating of 5.9, which is considered medium.
To fix CVE-2020-13254, you should update Django to version 2.2.13 or 3.0.7, depending on the version you are using.
You can find more information about CVE-2020-13254 on the NIST National Vulnerability Database (NVD) and Django's official security releases page.
The CWE (Common Weakness Enumeration) of CVE-2020-13254 is CWE-295, which is the category for Improper Certificate Validation.