CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AI Score
Confidence
High
EPSS
Percentile
69.0%
Azure RTOS USBX is a high-performance USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS ThreadX. The case is, in _ux_host_class_pima_read, there is data length from device response, returned in the very first packet, and read by L165 code, as header_length. Then in L178 code, there is a βifβ branch, which check the expression of β(header_length - UX_HOST_CLASS_PIMA_DATA_HEADER_SIZE) > data_lengthβ where if header_length is smaller than UX_HOST_CLASS_PIMA_DATA_HEADER_SIZE, calculation could overflow and then L182 code the calculation of data_length is also overflow, this way the later while loop start from L192 can move data_pointer to unexpected address and cause write buffer overflow. The fix has been included in USBX release 6.1.12. The following can be used as a workaround: Add check of header_length
: 1. It must be greater than UX_HOST_CLASS_PIMA_DATA_HEADER_SIZE
. 1. It should be greater or equal to the current returned data length (transfer_request -> ux_transfer_request_actual_length
).
Vendor | Product | Version | CPE |
---|---|---|---|
microsoft | azure_rtos_usbx | * | cpe:2.3:o:microsoft:azure_rtos_usbx:*:*:*:*:*:*:*:* |
[
{
"vendor": "azure-rtos",
"product": "usbx",
"versions": [
{
"version": "< 6.1.12",
"status": "affected"
}
]
}
]
More