RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1874496 - CVE-2020-24584 python-django: django: permission escalation in intermediate-level directories of the file system cache on Python 3.7+ [openstack-rdo]
Summary: CVE-2020-24584 python-django: django: permission escalation in intermediate-l...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: RDO
Classification: Community
Component: distribution
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: trunk
Assignee: Alfredo Moralejo
QA Contact: Shai Revivo
URL:
Whiteboard: component:python-django
Depends On:
Blocks: CVE-2020-24584
TreeView+ depends on / blocked
 
Reported: 2020-09-01 13:40 UTC by Guilherme de Almeida Suckevicz
Modified: 2020-12-03 15:05 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-12-03 15:05:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2020-09-01 13:40:09 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 Yatin Karel 2020-12-03 15:05:32 UTC
This flaw can only be triggered in Django by using Python version 3.7 and newer. While RDO Train+ releases ship Python 3.6.8; and before Train ship Python 2.X., the flaw cannot be activated without manually updating Python to a newer release which is unsupported, so closing the BZ as WONTFIX like parent BZ.


Note You need to log in before you can comment on or make changes to this bug.