Product
qualcomm qfe3100 firmware
34 known vulnerabilities across versions
Vulnerabilities are listed by affected version. Select any CVE for the full briefing and its intelligence graph.
CVE-2020-11238
CVE-2020-11235
CVE-2020-11233
CVE-2020-11159
CVE-2020-11126
CVE-2021-1925
CVE-2021-1905
CVE-2020-11293
CVE-2020-11289
CVE-2020-11285
CVE-2020-11279
CVE-2021-1892
CVE-2020-11251
CVE-2020-11234
CVE-2020-11191
CVE-2020-11227
CVE-2020-11226
CVE-2020-11221
CVE-2020-11199
CVE-2020-11192
CVE-2020-11190
CVE-2020-11189
CVE-2020-11188
CVE-2020-11171
CVE-2020-11166
CVE-2020-11296
CVE-2020-11276
CVE-2020-11275
CVE-2020-11269
CVE-2020-11204
CVE-2020-11195
CVE-2020-11177
CVE-2020-11170
CVE-2020-11119
all versions
Possible Buffer over-read in ARP/NS parsing due to lack of check of packet length received in Snapdragon Auto, Snapdragon Compute,
all versions
Buffer overflow might occur while parsing unified command due to lack of check of input data received in Snapdragon Auto, Snapdrag
all versions
Time-of-check time-of-use race condition While processing partition entries due to newly created buffer was read again from mmc wi
all versions
Buffer over-read can happen while processing WPA,RSN IE of beacon and response frames if IE length is less than length of frame po
all versions
Possible out of bound read while WLAN frame parsing due to lack of check for body and header length in Snapdragon Auto, Snapdragon
all versions
Possible denial of service scenario due to improper handling of group management action frame in Snapdragon Auto, Snapdragon Compu
all versions
Possible use after free due to improper handling of memory mapping of multiple processes simultaneously. in Snapdragon Auto, Snapd
all versions
Out of bound read can happen in Widevine TA while copying data to buffer from user data due to lack of check of buffer length rece
all versions
Out of bound write can occur in TZ command handler due to lack of validation of command ID in Snapdragon Auto, Snapdragon Compute,
all versions
Buffer over-read while unpacking the RTCP packet we may read extra byte if wrong length is provided in RTCP packets in Snapdragon
all versions
Memory corruption while processing crafted SDES packets due to improper length check in sdes packets recieved in Snapdragon Auto,
all versions
Memory corruption due to improper input validation while processing IO control which is nonstandard in Snapdragon Compute, Snapdra
all versions
Out-of-bounds read vulnerability while accessing DTMF payload due to lack of check of buffer length before copying in Snapdragon A
all versions
When sending a socket event message to a user application, invalid information will be passed if socket is freed by other thread r
all versions
Out of bound read occurs while processing crafted SDP due to lack of check of null string in Snapdragon Auto, Snapdragon Compute,
all versions
Out of bound write while parsing RTT/TTY packet parsing due to lack of check of buffer size before copying into buffer in Snapdrag
all versions
Out of bound memory read in Data modem while unpacking data due to lack of offset length check in Snapdragon Auto, Snapdragon Comp
all versions
Usage of syscall by non-secure entity can allow extraction of secure QTEE diagnostic information in clear text form due to insuffi
all versions
HLOS to access EL3 stack canary by just mapping imem region due to Improper access control and can lead to information exposure in
all versions
Out of bound write while parsing SDP string due to missing check on null termination in Snapdragon Auto, Snapdragon Compute, Snapd
all versions
Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Sna
all versions
Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Sna
all versions
Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Sna
all versions
Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Sna
all versions
Potential out of bound read exception when UE receives unusually large number of padding octets in the beginning of ROHC header in
all versions
Arithmetic overflow can happen while processing NOA IE due to improper error handling in Snapdragon Auto, Snapdragon Compute, Snap
all versions
Possible buffer over read while processing P2P IE and NOA attribute of beacon and probe response frames due to improper validation
all versions
Possible buffer over-read while parsing quiet IE in Rx beacon frame due to improper check of IE length in received beacon in Snapd
all versions
Possible memory corruption while processing EAPOL frames due to lack of validation of key length before using it in Snapdragon Aut
all versions
Possible memory corruption and information leakage in sub-system due to lack of check for validity and boundary compliance for par
all versions
Out of bound write and read in TA while processing command from NS side due to improper length check on command and response buffe
all versions
User can overwrite Security Code NV item without knowing current SPC due to improper validation of SPC code setting and device loc
all versions
Out of bound memory access while playing music playbacks with crafted vorbis content due to improper checks in header extraction i
all versions
Buffer over-read can happen when the buffer length received from response handlers is more than the size of the payload in Snapdra