Bug 913043

Summary:	CVE-2013-0305 CVE-2013-0306 Django various flaws [epel-5]
Product:	[Fedora] Fedora EPEL	Reporter:	Kurt Seifried <kseifried>
Component:	Django	Assignee:	Steve Milner <smilner>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	el5	CC:	apevec, dmalcolm, michel, mrunge, smilner, thoger
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-20 13:25:24 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:	913037, 913039, 913041, 913042

Description Kurt Seifried 2013-02-20 09:32:46 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 Fedora EPEL.

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 creating a Bodhi update request, please use the bodhi submission link
noted 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
Bodhi notes field when available.

epel-5 tracking bug for Django: see blocks bug list for full details of the security issue(s).

[bug automatically created by: add-tracking-bugs]

Comment 1 Kurt Seifried 2013-02-20 09:32:53 UTC

Please use the following update submission link to create the Bodhi
request for this issue as it contains the top-level parent bug(s) as well
as this tracking bug.  This will ensure that all associated bugs get
updated when new packages are pushed to stable.

Please also ensure that the "Close bugs when update is stable" option
remains checked.

Bodhi update submission link:
https://admin.fedoraproject.org/updates/new/?type_=security&bugs=913037,913043

Comment 2 Kurt Seifried 2013-02-20 09:33:11 UTC

Adding parent bug 913039.  Please use this new bodhi update url when correcting
these flaws:

https://admin.fedoraproject.org/updates/new/?type_=security&bugs=913043,913037,913039

Comment 3 Kurt Seifried 2013-02-20 09:33:33 UTC

Adding parent bug CVE-2013-0305.  Please use this new bodhi update url when correcting
these flaws:

https://admin.fedoraproject.org/updates/new/?type_=security&bugs=913043,913037,913039,913041

Comment 4 Kurt Seifried 2013-02-20 09:33:53 UTC

Adding parent bug CVE-2013-0306.  Please use this new bodhi update url when correcting
these flaws:

https://admin.fedoraproject.org/updates/new/?type_=security&bugs=913043,913037,913039,913041,913042

Comment 5 Matthias Runge 2013-03-20 13:25:24 UTC

Django on EPEL5 is Django-1.1, it doesn't receive any updates any more since Django-1.3 was released, and that has been a loooong time.

Comment 6 Tomas Hoger 2013-03-20 15:23:27 UTC

Can you make sure it's properly obsoleted and removed form EPEL if it's no longer updated with security fixes?

Comment 7 Matthias Runge 2013-03-20 15:52:05 UTC

Never Django versions require never python versions, e.g. Django 1.5 (current version) requires python2.7 or python 3. 

Of course I can deprecate and retire from EPEL5, but what does this help?

Comment 8 Michel Lind 2013-03-21 03:10:21 UTC

We don't want to ship packages that contain security vulnerabilities, I suppose, especially when alternatives exist (people who really want to use Django on EL5 could install Django 1.4.x on top of python26-virtualenv - though when Django 1.4.x also goes out of support they'd be in a pickle)

Comment 9 Tomas Hoger 2013-03-21 19:00:28 UTC

As explained by Michel, keeping known vulnerable and known unsupported package around is not ideal.  Its removal can also prevent similar future bugs.

Comment 10 Matthias Runge 2013-03-22 07:07:45 UTC

I absolutely agree, I've sent a mail about retiring Django-1.1 to epel-devel list:
https://www.redhat.com/archives/epel-devel-list/2013-March/msg00036.html