MySQL Announce List email :
This release also resolves a crashing bug that could be exploited as a
potential local Denial of Service attack,
We would like to thank Stefan Streichsbier from SEC Consult, who also
informed us about this bug via our email@example.com mail address - he
will send out a separate advisory about his findings.
Could mysql be updated to 5.0.37 anytime soon, or at least have the patches
backported ? There are more bugs fixed, fe. :
* Some CASE statements inside stored routines could lead to excessive resource
usage or a crash of the server. (Bug#24854, Bug#19194)
* Some joins in which one of the joined tables was a view could return
erroneous results or crash the server. (Bug#24345)
Many thanks :)
The MySQL folk don't seem to think that 5.0.37 is a security release, and I
don't plan to treat it as one. I've built it in rawhide and will consider
pushing it into FC6 if there are not too many squawks; but the list of
incompatibilities seems a bit worrisome.
Hi! What incompatabilities are you referring to?
Read the release notes for yourself ... the one that sticks in my mind at 12:50AM local time is a potential
forced dump-and-reload for enum columns. There were a few others that seemed a bit questionable for
an allegedly stable release branch.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.