Bug 1727697

Summary:	CVE-2019-12781 python-django: Django: Incorrect HTTP detection with reverse-proxy connecting via HTTPS [openstack-rdo]
Product:	[Community] RDO	Reporter:	Summer Long <slong>
Component:	distribution	Assignee:	Alfredo Moralejo <amoralej>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Shai Revivo <srevivo>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	dbecker, jjoyce, jschluet, lhh, lpeer, markmc, mburns, sclewis, slinaber, srevivo
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	trunk
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	component:python-django
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-23 10:14: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:
Embargoed:
Bug Depends On:
Bug Blocks:	1724497

Description Summer Long 2019-07-08 03:52:29 UTC

This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of openstack-rdo.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

Comment 1 Alfredo Moralejo 2020-07-23 10:14:43 UTC

RDO Ussuri and Victoria are shiping python-django-2.2.9 which has the fix.
Train for CentOS 8 is capped to django 2.0 which doesn't provide the fix. This CVE has moderate category so, it's not worthy to use a non-tested upstream release of django for it.