Bug 481171 - update rt3 to 3.6.7
Summary: update rt3 to 3.6.7
Alias: None
Product: Fedora
Classification: Fedora
Component: rt3
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ralf Corsepius
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-01-22 15:45 UTC by Xavier Bachelot
Modified: 2009-07-15 08:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-07-15 08:25:33 UTC

Attachments (Terms of Use)

Description Xavier Bachelot 2009-01-22 15:45:41 UTC
Description of problem:
rt3 <= 3.6.6 is vulnerable to a DoS attack thru the perl-Devel-StackTrace <
1.19 vector. Both the perl module and rt 3.6.7 are needed to fully fix the security issue. 

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3502 and
http://lists.bestpractical.com/pipermail/rt-announce/2008-June/000158.html for

Comment 1 Tomas Hoger 2009-01-23 07:59:58 UTC
Actually, upstream announcement is worded bit differently:

  Installing this newer version of the module is a complete fix, and
  will close the vulnerability.

New RT only seems to have additional protections for possible (but currently unknown) similar issue.

perl-Devel-StackTrace 1.20 that should fix this is already in all Fedora versions.

Comment 2 Ralf Corsepius 2009-01-23 08:11:15 UTC
(In reply to comment #1)
> New RT only seems to have additional protections for possible (but currently
> unknown) similar issue.
> perl-Devel-StackTrace 1.20 that should fix this is already in all Fedora
> versions.
This interpretation matches with mine. 

Independently, I've pushed rt3-3.6.7 to fc9/testing, because it already had been part of "devel"/rawhide for some time during FC10 development, but had never made it into "stable".

Whether I'll push this package to FC9/stable is a different matters.

My problem: I don't have access to an FC9 anymore.

Comment 3 Fedora Update System 2009-01-24 02:32:06 UTC
rt3-3.6.7-1.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing-newkey update rt3'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2009-0868

Comment 4 Bug Zapper 2009-06-10 03:30:17 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 5 Bug Zapper 2009-07-15 08:25:33 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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