ESF-IDF is the Espressif Internet of Things (IOT) Development Framework

Why it is Yellow

• CVSS 6.5 medium

References

• https://github.com/espressif/esp-idf/commit/14c99559b4337cabcf0f09c21d16b93c4cd7a6fe
• https://github.com/espressif/esp-idf/commit/1e07f6d83ca892630a7210df2958455f7ca77b4a
• https://github.com/espressif/esp-idf/commit/5731c63ece128f156939b9f734256e2227c1442a
• https://github.com/espressif/esp-idf/commit/8de265dc44b1b22c749ea44ee7c609b3da4162f0
• https://github.com/espressif/esp-idf/commit/9a6d04f65e0e341e7d72bd417c9f31b8a04ce846
• https://github.com/espressif/esp-idf/commit/c2610255a5adce651ca582bb82368c3dd0ee2834
• https://github.com/espressif/esp-idf/commit/c8cd8f4f3019ae2f912c8cbe9974445e8d9b8749
• https://github.com/espressif/esp-idf/releases/tag/v5.2.8
• https://github.com/espressif/esp-idf/releases/tag/v5.3.6
• https://github.com/espressif/esp-idf/releases/tag/v5.5.5

Original description

ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. Prior to 5.2.8, 5.3.6, 5.5.5, 6.0.3, and 6.1-rc1, ESP-IDF BlueDroid L2CAP configuration-option processing in l2c_main.c and l2c_utils.c does not consistently validate option lengths against the remaining received packet bytes. A remote unauthenticated BR/EDR peer within radio range can send a malformed L2CAP configuration request that causes an out-of-bounds read, and under some runtime conditions limited adjacent Bluetooth stack memory can be included in an outbound L2CAP Configuration Response. The issue affects ESP32-class products using the BlueDroid host stack with Classic Bluetooth enabled. This issue is fixed in 5.2.8, 5.3.6, 5.5.5, 6.0.3, and 6.1-rc1.