Qi Xu
Qi Xu
When I successfully complie and run the broker, many memory leaks occurs:
I triggered a stack-buffer-overflow(heap-use-after-free) bug reported by AddressSanitizer when fuzzing sol. It occurs when memory that has already been freed is accessed again. According to the AddressSanitizer output, the issue...
## Description A segmentation fault has been triggered because Azure uAMQP continues to drive the TLS handshake state machine in `send_handshake_bytes()` even after OpenSSL enters an unrecoverable internal error state...
## Description When running message_sender_sample from azure-uamqp-c, the process can crash with a segmentation fault during startup, inside OpenSSL configuration cleanup (_CONF_free_data), triggered by a NULL return from OpenSSL APIs....
## Description When using Azure uAMQP-C with OpenSSL 1.1.x, a segmentation fault can be triggered during TLS initialization if certain OpenSSL X509 APIs return valid failure values. ## Environment -...