Hi, Kurt! This is CVE-2012-5579 that we've been discussing recently. A test case it different, but it triggers exactly the same code. MariaDB is not vulnerable as of 5.1.66, 5.2.13, 5.3.11, 5.5.28a. Latest released MySQL versions are still affected, but Oracle knows about this issue, so next versions won't be. Regards, Sergei MariaDB Security Coordinator On Dec 01, Kurt Seifried wrote: > On 12/01/2012 02:26 PM, king cope wrote: > > (see attachment) > > > > Cheerio, Kingcope > > So normally for MySQL issues Oracle would assign the CVE #. However in > this case we have a bit of a time constraint (it's a weekend and this > is blowing up quickly) and the impacts are potentially quite severe. > So I've spoken with some other Red Hat SRT members and we feel it is > best to get CVE #'s assigned for these issues quickly so we can refer > to them properly. > > If Oracle security has already assigned CVE's for these please let us > and the public know so we can use the correct numbers. Also if Oracle > can let the public know which versions of MySQL are affected (e.g. > 5.0.x, 5.1.x, 5.5.x, etc.) that would be very helpful to everyone I am > sure. > > I am also adding MySQL, Oracle, MariaDB, OSS-SEC, Steven Christey, > cve-assign and OSVDB to the CC so that everyone is aware of what is > going on. > > http://seclists.org/fulldisclosure/2012/Dec/4 >
