CVE-2022-39293
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
Summary
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).
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| azure-rtos | usbx | < 6.1.12 | affected |
Weaknesses
- CWE-191: CWE-191: Integer Underflow (Wrap or Wraparound)
ADP Enrichment
CVE Program Container
Additional References
- https://github.com/azure-rtos/usbx/releases/tag/v6.1.12_rel
- https://github.com/azure-rtos/usbx/security/advisories/GHSA-gg76-h537-xq48
CISA ADP Vulnrichment
- SSVC:
- Exploitation: none
- Automatable: yes
- Technical Impact: partial
References
- https://github.com/azure-rtos/usbx/releases/tag/v6.1.12_rel
- https://github.com/azure-rtos/usbx/security/advisories/GHSA-gg76-h537-xq48
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.