This bug is for Oracle Critical Patch Update Advisory - July 2012 planned to be released on July 17 and that is expected to list several MySQL flaws:
So far, MySQL versions 5.1.63, 5.5.23, 5.5.24, and 5.5.25:
were released in the last CPU in April 2012:
which covered fixes in version 5.1.62 and 5.5.22. Apr 2012 CPU is covered by bug #832477.
This bug attempts to list issues that were already made public via released MySQL versions or bazaar commits.
A rather important password verification flaw was disclosed recently and got CVE-2012-2122 assigned. Refer to bug 814605 for details.
5.1.63 and 5.5.24 release notes mention this security fix:
* Security Fix: Bug #64884 was fixed.
Bug #13934049: 64884: LOGINS WITH INCORRECT PASSWORD ARE ALLOWED
Another security fix mentioned in the 5.1.63 released notes is:
* Security Fix: Bug #59387 was fixed.
Matching upstream commit is:
Bug#11766300 59387: FAILING ASSERTION: CURSOR->POS_STATE == 1997660512 (BTR_PCUR_IS_POSITIONE
Bug#13639204 64111: CRASH ON SELECT SUBQUERY WITH NON UNIQUE INDEX
This issue allows non-admin database user with full SQL access to crash mysqld.
It is also fixed in 5.5.24, but is not mentioned in the release notes or the changelog file bundled in the source tarball. This issue also affects MySQL 5.0.
5.5.23 release notes mention:
* Security Fix: Bug #59533 was fixed.
I'm currently unable to find any commit that references mentioned bug.
Oracle July CPU to be released on Jul 17 will fix 6 MySQL issues according to the pre-release announcement:
(In reply to comment #0)
> So far, MySQL versions 5.1.63, 5.5.23, 5.5.24, and 5.5.25:
Oracle July CPU only describes MySQL issues fixed in versions 5.1.63, 5.5.23, and 5.5.24. Even though 5.5.25 and 5.5.25a were released before the CPU release, it may mean that they don't include any security fixes or that they will only be announced in the next CPU in October.