CVE-2022-29246

{"id": "CVE-2022-29246", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 7.5, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "LOW", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "HIGH", "obtainAllPrivilege": false, "exploitabilityScore": 10.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}]}, "published": "2022-05-24T15:15:08.160", "references": [{"url": "https://github.com/azure-rtos/usbx/blob/master/common/usbx_device_classes/src/ux_device_class_dfu_control_request.c", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/azure-rtos/usbx/releases/tag/v6.1.11_rel", "tags": ["Release Notes", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/azure-rtos/usbx/security/advisories/GHSA-hh5p-x584-j8hv", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/azure-rtos/usbx/blob/master/common/usbx_device_classes/src/ux_device_class_dfu_control_request.c", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/azure-rtos/usbx/releases/tag/v6.1.11_rel", "tags": ["Release Notes", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/azure-rtos/usbx/security/advisories/GHSA-hh5p-x584-j8hv", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-120"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Azure RTOS USBX es una pila embebida de host USB, dispositivo y on-the-go (OTG). En versiones anteriores a 6.1.11, la funcionalidad USBX DFU UPLOAD puede ser usada para introducir un desbordamiento de b\u00fafer que resulta en la sobreescritura del contenido de la memoria. En determinados casos, esto puede permitir a un atacante omitir las funciones de seguridad o ejecutar c\u00f3digo arbitrario. La implementaci\u00f3n de la funci\u00f3n \"ux_device_class_dfu_control_request\" no asegura que no sea producida un desbordamiento del b\u00fafer durante el manejo del comando DFU UPLOAD. Cuando un atacante emite la petici\u00f3n de transferencia de control \"UX_SLAVE_CLASS_DFU_COMMAND_UPLOAD\" con \"wLenght\" mayor que el tama\u00f1o del buffer (\"UX_SLAVE_REQUEST_CONTROL_MAX_LENGTH\", 256 bytes), dependiendo de la implementaci\u00f3n real de \"dfu -) ux_slave_class_dfu_read\", puede producirse un desbordamiento del buffer. Por ejemplo, \"ux_slave_class_dfu_read\" puede leer 4096 bytes (o m\u00e1s hasta 65k) en un buffer de 256 bytes, resultando en un desbordamiento. Adem\u00e1s, en caso de que un atacante tenga alg\u00fan control sobre la memoria flash le\u00edda, esto puede resultar en una ejecuci\u00f3n de c\u00f3digo arbitrario y el compromiso de la plataforma. Ha sido incluida una correcci\u00f3n para este problema en versi\u00f3n 6.1.11 de USBX. Como mitigaci\u00f3n, alinee la petici\u00f3n y el tama\u00f1o del b\u00fafer para asegurarse de que sean respetados los l\u00edmites del b\u00fafer"}], "lastModified": "2024-11-21T06:58:47.920", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:microsoft:azure_rtos_usbx:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "930D9474-0A8D-423B-AE4C-0E719ED5F6A2", "versionEndExcluding": "6.1.11"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}