Vulnerabilidades em Qualcomm, Inc.

2.991 resultados
Análise Vexday

Com 2.934 CVEs catalogadas, a Qualcomm apresenta um volume expressivo de vulnerabilidades, reflexo da amplitude de seu portfólio de chipsets e firmware embarcado. A taxa de exploração ativa — 12 entradas no catálogo KEV da CISA, ou 0,41% do total — está em linha com a média geral do catálogo, indicando que o risco de exploração confirmada não foge do padrão da indústria, embora 94 falhas de severidade crítica representem uma superfície de ataque relevante para equipes de segurança que dependem de componentes Qualcomm em ambientes móveis, automotivos ou de IoT. A CVE mais perigosa atualmente em exploração ativa, CVE-2020-11261, apresenta EPSS de 0,0177, sugerindo probabilidade de exploração adicional relativamente baixa no curto prazo, mas sua presença no KEV exige atenção imediata em qualquer inventário de ativos afetados. O surgimento de 49 novas CVEs nos últimos 90 dias e a disponibilidade de PoCs públicas para 3 vulnerabilidades reforçam a necessidade de ciclos contínuos de atualização de firmware e monitoramento ativo de patches liberados pelo fabricante.

CVE-2016-10237—If shared content protection memory were passed as the secure camera memory buffer by the HLOS to a trusted application (TA) in all Android EPSS 0.6%CVE-2021-1907HIGHPossible buffer overflow due to lack of length check in BA request in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, SnapdragEPSS 0.6%CVE-2021-30310HIGHPossible buffer overflow due to Improper validation of received CF-ACK and CF-Poll data frames in Snapdragon Auto, Snapdragon Connectivity, EPSS 0.6%CVE-2024-33066CRITICALImproper Input Validation in WLAN Resource ManagerEPSS 0.6%CVE-2022-22086HIGHMemory corruption in video due to double free while parsing 3gp clip with invalid meta data atoms in Snapdragon Auto, Snapdragon Compute, SnEPSS 0.6%CVE-2016-5867—In a sound driver in Android for MSM, Firefox OS for MSM, QRD Android, some variables are from userspace and values can be chosen that couldEPSS 0.6%CVE-2017-14876—In msm_ispif_config_stereo() in Android for MSM, Firefox OS for MSM, and QRD Android before 2017-06-21, the parameter params->entries[i].vfeEPSS 0.6%CVE-2017-14881—While calling the IPA IOCTL handler for IPA_IOC_ADD_HDR_PROC_CTX in Android for MSM, Firefox OS for MSM, and QRD Android before 2017-10-13, EPSS 0.6%CVE-2017-14877—While the IPA driver in Android for MSM, Firefox OS for MSM, and QRD Android before 2017-08-31 is processing IOCTL commands there is no muteEPSS 0.6%CVE-2021-30300HIGHPossible denial of service due to incorrectly decoding hex data for the SIB2 OTA message and assigning a garbage value to choice when procesEPSS 0.6%CVE-2021-30330HIGHPossible null pointer dereference due to improper validation of APE clip in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, SnEPSS 0.6%CVE-2021-1914HIGHLoop with unreachable exit condition may occur due to improper handling of unsupported input in Snapdragon Auto, Snapdragon Compute, SnapdraEPSS 0.6%CVE-2021-30287HIGHPossible assertion due to improper validation of symbols configured for PDCCH monitoring in Snapdragon Auto, Snapdragon Compute, Snapdragon EPSS 0.6%CVE-2021-30307HIGHPossible denial of service due to improper validation of DNS response when DNS client requests with PTR, NAPTR or SRV query type in SnapdragEPSS 0.6%CVE-2021-1982HIGHPossible denial of service scenario due to improper input validation of received NAS OTA message in Snapdragon Auto, Snapdragon Compute, SnaEPSS 0.6%CVE-2021-30273HIGHPossible assertion due to improper handling of IPV6 packet with invalid length in destination options header in Snapdragon Auto, Snapdragon EPSS 0.6%CVE-2021-1964HIGHPossible buffer over read due to improper validation of IE size while parsing beacon from peer device in Snapdragon Auto, Snapdragon ComputeEPSS 0.6%CVE-2021-1937HIGHReachable assertion is possible while processing peer association WLAN message from host and nonstandard incoming packet in Snapdragon Auto,EPSS 0.6%CVE-2021-1953HIGHImproper handling of received malformed FTMR request frame can lead to reachable assertion while responding with FTM1 frame in Snapdragon AuEPSS 0.6%CVE-2021-30353HIGHImproper validation of function pointer type with actual function signature can lead to assertion in Snapdragon Auto, Snapdragon Compute, SnEPSS 0.6%