| Summary: | CVE-2020-13254 django: potential data leakage via malformed memcached keys | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Guilherme de Almeida Suckevicz <gsuckevi> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | andrea.manzi, apevec, bbuckingham, bcourt, bkearney, btotty, dbecker, hhudgeon, hvyas, jal233, jjoyce, jschluet, lhh, lpeer, lzap, mburns, mhroncok, michal.simon, michel, mmccune, mrunge, nmoumoul, puebele, pviktori, rchan, rdopiera, rhos-maint, rjerrido, sclewis, sgallagh, slavek.kabrda, slinaber, sokeeffe |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Django-3.0.7, Django-2.2.13 | Doc Type: | If docs needed, set a value |
| Doc Text: |
A flaw was found in Django, where the memcached backend does not perform key validation and passes malformed keys. This flaw causes a key collision and potential data leakage. The highest threat from this vulnerability is to confidentiality.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-03-17 19:51:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1843618, 1843620, 1843616, 1843617, 1843619, 1844992, 1845340, 1845341, 1845342, 1845442, 1845455, 1845729, 1852453 | ||
| Bug Blocks: | 1843622 | ||
|
Description
Guilherme de Almeida Suckevicz
2020-06-03 16:41:32 UTC
Created django:1.6/python-django tracking bugs for this issue: Affects: fedora-all [bug 1843620] Created python-django tracking bugs for this issue: Affects: epel-all [bug 1843616] Affects: fedora-all [bug 1843617] Affects: openstack-rdo [bug 1843619] Created python-django16 tracking bugs for this issue: Affects: epel-7 [bug 1843618] External References: https://www.djangoproject.com/weblog/2020/jun/03/security-releases Upstream patches: https://github.com/django/django/commit/2c82414914ae6476be5a166be9ff49c24d0d9069 https://github.com/django/django/commit/229c9c6653356a0bc23846d83b2d4b5d0438a145 Created python2-django1.11 tracking bugs for this issue: Affects: fedora-all [bug 1845442] Statement: Red Hat Satellite 6 ships affected python-django, however, it does not use memcached implementation in product code hence not vulnerable to this flaw. Red Hat Update Infrastructure 3 ships an affected version of python-django, however it does not use memcached as a cache backend and it is not vulnerable to this flaw. Red Hat Ceph Storage(RHCS) ships an affected version of python-django used with calamari and graphite which are no longer supported, hence the django package will not be fixed for RHCS. This issue has been addressed in the following products: Red Hat OpenStack Platform 16.1 Via RHSA-2021:0915 https://access.redhat.com/errata/RHSA-2021:0915 This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2020-13254 This issue has been addressed in the following products: Red Hat OpenStack Platform 13.0 (Queens) Red Hat OpenStack Platform 13.0 (Queens) for RHEL 7.6 EUS Via RHSA-2021:0933 https://access.redhat.com/errata/RHSA-2021:0933 |