Vulnerabilities > Qualcomm > Qcn9011 Firmware
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-02-12 | CVE-2022-33232 | Classic Buffer Overflow vulnerability in Qualcomm products Memory corruption due to buffer copy without checking size of input while running memory sharing tests with large scattered memory. | 7.8 |
2023-02-12 | CVE-2022-33271 | Out-of-bounds Read vulnerability in Qualcomm products Information disclosure due to buffer over-read in WLAN while parsing NMF frame. | 7.5 |
2023-02-12 | CVE-2022-33277 | Classic Buffer Overflow vulnerability in Qualcomm products Memory corruption in modem due to buffer copy without checking size of input while receiving WMI command. | 7.8 |
2023-02-12 | CVE-2022-33279 | Out-of-bounds Write vulnerability in Qualcomm products Memory corruption due to stack based buffer overflow in WLAN having invalid WNM frame length. | 9.8 |
2023-02-12 | CVE-2022-33280 | Access of Uninitialized Pointer vulnerability in Qualcomm products Memory corruption due to access of uninitialized pointer in Bluetooth HOST while processing the AVRCP packet. | 8.8 |
2023-02-12 | CVE-2022-40512 | Out-of-bounds Read vulnerability in Qualcomm products Transient DOS in WLAN Firmware due to buffer over-read while processing probe response or beacon. | 7.5 |
2023-02-12 | CVE-2022-40514 | Out-of-bounds Write vulnerability in Qualcomm products Memory corruption due to buffer copy without checking the size of input in WLAN Firmware while processing CCKM IE in reassoc response frame. | 9.8 |
2023-01-09 | CVE-2022-22088 | Out-of-bounds Write vulnerability in Qualcomm products Memory corruption in Bluetooth HOST due to buffer overflow while parsing the command response received from remote | 8.8 |
2023-01-09 | CVE-2022-25746 | Classic Buffer Overflow vulnerability in Qualcomm products Memory corruption in kernel due to missing checks when updating the access rights of a memextent mapping. | 7.8 |
2023-01-09 | CVE-2022-33252 | Out-of-bounds Read vulnerability in Qualcomm products Information disclosure due to buffer over-read in WLAN while handling IBSS beacons frame. | 5.5 |