Possible segmentation fault in application callback function caused by not properly initialized argument

[jpwsutton]

migrated from Bugzilla #486548
status UNCONFIRMED severity normal in component MQTT-C for 1.2
Reported in version 1.2 on platform PC
Assigned to: Ian Craggs

Original attachment names and IDs:

• commit-e1d8e2d (ID 259382)

On 2016-01-26 07:15:05 -0500, Juergen Kosel wrote:

The functions MQTTAsync_removeResponsesAndCommands() and
MQTTAsync_removeResponsesAndCommands() do not initialize the pointer data.message.
So if a on command failure callback tries to use this given pointer,
it has no chance to see that there is no valid message. And then it triggers a
segmentation fault exception.

On 2016-01-26 07:16:37 -0500, Juergen Kosel wrote:

Created attachment 259382
Git commit which fixes this problem

Initialize the message to null pointer

To prevent segmentation fault in application, the message pointer needs
to be initialized.

[icraggs]

Fix added to the develop branch.