The legacy channels.http.AsgiHandler class, used for handling HTTP type requests in an ASGI environment prior to Django 3.0, did not correctly separate request scopes in Channels 3.0. In many cases this would result in a crash but, with correct timing responses could be sent to the wrong client, resulting in potential leakage of session identifiers and other sensitive data. Reference: https://channels.readthedocs.io/en/latest/releases/3.0.3.html
Created python-django tracking bugs for this issue: Affects: fedora-all [bug 1911638]
This is not a flaw in the core Django, but in the Channels package for Django. This should not affect any "python-django" packages as shipped in Red Hat products or Fedora.
This seems to be the upstream commit: https://github.com/django/channels/commit/e85874d9630474986a6937430eac52db79a2a022 Related bug report and MR: https://github.com/django/channels/issues/1578 https://github.com/django/channels/pull/1581
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-35681