ID 413796 - Crash when ZMQ socket receives bad data

Problem summary:

When bad data is fed to Katana via the ZeroMQ sockets, Katana may crash.

Steps to reproduce (crash #1):

• Launch Katana.
• Run the following command to find out which Katana port we want to talk to (typically 16000, but it could be 16001 or following ports if they are busy):

sudo lsof -i -P -n | grep katanaBin

• Using zmqc, send four bytes to Katana (the fact that the second byte is 0x00 will crash Katana):

echo -n -e '\xAA\x00\x05\x00' | zmqc -wc PUSH 'tcp://0.0.0.0:16000'

• Katana will potentially crash.

echo -n -e '\xAA\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' | zmqc -wc PUSH 'tcp://0.0.0.0:16000'

Tested versions/platforms:

• 3.0v9 - Affected
• 3.1v7 - Affected
• 3.2v2 - Affected
• 3.2v2 - Affected