{"timestamp":"2025-04-23T15:49:31.898232Z","id":"CVE-2022-29246","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}

[{"vendor":"azure-rtos","product":"usbx","versions":[{"version":"< 6.1.11","status":"affected"}]}]

OR
     *cpe:2.3:o:microsoft:azure_rtos_usbx:*:*:*:*:*:*:*:* versions from (excluding) 6.1.11

OR
     *cpe:2.3:a:eclipse:threadx_usbx:*:*:*:*:*:*:*:* versions from (excluding) 6.1.11

https://github.com/azure-rtos/usbx/blob/master/common/usbx_device_classes/src/ux_device_class_dfu_control_request.c

https://github.com/azure-rtos/usbx/releases/tag/v6.1.11_rel

https://github.com/azure-rtos/usbx/security/advisories/GHSA-hh5p-x584-j8hv

NIST AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

NIST (AV:N/AC:L/Au:N/C:P/I:P/A:P)

OR
     *cpe:2.3:o:microsoft:azure_rtos_usbx:*:*:*:*:*:*:*:* versions up to (excluding) 6.1.11

https://github.com/azure-rtos/usbx/blob/master/common/usbx_device_classes/src/ux_device_class_dfu_control_request.c No Types Assigned

https://github.com/azure-rtos/usbx/blob/master/common/usbx_device_classes/src/ux_device_class_dfu_control_request.c Third Party Advisory

https://github.com/azure-rtos/usbx/releases/tag/v6.1.11_rel No Types Assigned

https://github.com/azure-rtos/usbx/releases/tag/v6.1.11_rel Release Notes, Third Party Advisory

https://github.com/azure-rtos/usbx/security/advisories/GHSA-hh5p-x584-j8hv No Types Assigned

https://github.com/azure-rtos/usbx/security/advisories/GHSA-hh5p-x584-j8hv Third Party Advisory

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack. Prior to version 6.1.11, he USBX DFU UPLOAD functionality may be utilized to introduce a buffer overflow resulting in overwrite of memory contents. In particular cases this may allow an attacker to bypass security features or execute arbitrary code. The implementation of `ux_device_class_dfu_control_request` function does not assure that a buffer overflow will not occur during handling of the DFU UPLOAD command. When an attacker issues the `UX_SLAVE_CLASS_DFU_COMMAND_UPLOAD` control transfer request with `wLenght` larger than the buffer size (`UX_SLAVE_REQUEST_CONTROL_MAX_LENGTH`, 256 bytes), depending on the actual implementation of `dfu -> ux_slave_class_dfu_read`, a buffer overflow may occur. In example `ux_slave_class_dfu_read` may read 4096 bytes (or more up to 65k) to a 256 byte buffer ultimately resulting in an overflow. Furthermore in case an attacker has some control over the read flash memory, this may result in execution of arbitrary code and platform compromise. A fix  for this issue has been included in USBX release 6.1.11. As a workaround, align request and buffer size to assure that buffer boundaries are respected.

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack. Prior to version 6.1.11, he USBX DFU UPLOAD functionality may be utilized to introduce a buffer overflow resulting in overwrite of memory contents. In particular cases this may allow an attacker to bypass security features or execute arbitrary code. The implementation of `ux_device_class_dfu_control_request` function does not assure that a buffer overflow will not occur during handling of the DFU UPLOAD command. When an attacker issues the `UX_SLAVE_CLASS_DFU_COMMAND_UPLOAD` control transfer request with `wLenght` larger than the buffer size (`UX_SLAVE_REQUEST_CONTROL_MAX_LENGTH`, 256 bytes), depending on the actual implementation of `dfu -> ux_slave_class_dfu_read`, a buffer overflow may occur. In example `ux_slave_class_dfu_read` may read 4096 bytes (or more up to 65k) to a 256 byte buffer ultimately resulting in an overflow. Furthermore in case an attacker has some control over the read flash memory, this may result in execution of arbitrary code and platform compromise. A fix for this issue has been included in USBX release 6.1.11. As a workaround, align request and buffer size to assure that buffer boundaries are respected.