By recent security breach, do you mean the issue with passwords? If so:
for i in `seq 1 2000`; do mysql -u USERNAME --password=INCORRECTPASSWORD -h HOSTNAME ;
If you get in using that, you're vulnerable.
But as Harald said, why not just update? Always better to be patched and up-to-date.
From: Sabika Makhdoom [mailto:sabika.makhdoom@stripped]
Sent: Monday, June 25, 2012 12:17 AM
Subject: Question about testing memcmp()
I want to test our memcmp() binaries to see if we have the mysql binaries that are
impacted by the recent security breach. How do I test it?
Life was meant to be mobile
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
Notice: This communication may contain privileged and/or confidential information. If you
are not the intended recipient, please notify the sender by email, and immediately delete
the message and any attachments without copying or disclosing them. LBI may, for any
reason, intercept, access, use, and disclose any information that is communicated by or
through, or which is stored on, its networks, applications, services, and devices.