This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained.

Perhaps the lack of such an indicator is because this bug was filed over two years ago?

We have long since patched around it and are not likely to spend any resources further investigating it.

(As an aside, the amount of work required in migrating to 5.0 makes it unlikely that we'll do so any time soon – frankly I don't see the benefits for us at this time.)