Security Vulnerability - Action Required: BufferOverflow vulnerability may in your project

[Crispy-fried-chicken]

Hi,
we have detected that your project may be vulnerable to bufferoverflow in the function of int send_chunk (CONCRETE_IO_HANDLE tls_io,const void* buffer,size_t size,ON_SEND_COMPLETE on_send_complete,void* callback_context) in the file of samples/local_server_tls_sample/tls_server_io_schannel.c . It shares similarities to a recent CVE disclosure CVE-2024-29195 in the azure-c-shared-utility.

The source vulnerability information is as follows:

Vulnerability Detail:
CVE Identifier: CVE-2024-29195
Description: The azure-c-shared-utility is a C library for AMQP/MQTT communication to Azure Cloud Services. This library may be used by the Azure IoT C SDK for communication between IoT Hub and IoT Hub devices. An attacker can cause an integer wraparound or under-allocation or heap buffer overflow due to vulnerabilities in parameter checking mechanism, by exploiting the buffer length parameter in Azure C SDK, which may lead to remote code execution. Requirements for RCE are 1. Compromised Azure account allowing malformed payloads to be sent to the device via IoT Hub service, 2. By passing IoT hub service max message payload limit of 128KB, and 3. Ability to overwrite code space with remote code. Fixed in commit Azure/azure-c-shared-utility@1129147.
Reference: https://nvd.nist.gov/vuln/detail/CVE-2024-29195
Patch: Azure/azure-c-shared-utility@1129147

Would you help to check if this bug is true? If it's true, I'd like to open a PR for that if necessary. Thank you for your effort and patience!