Vulnerabilidades em Qualcomm, Inc.

2.976 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-2015-9030—In all Android releases from CAF using the Linux kernel, the Hypervisor API could be misused to bypass authentication.EPSS 0.8%CVE-2018-5876—While parsing an mp4 file, a buffer overflow can occur in Snapdragon Automobile, Snapdragon Mobile and Snapdragon Wear.EPSS 0.8%CVE-2018-5874—While parsing an mp4 file, a stack-based buffer overflow can occur in Snapdragon Automobile, Snapdragon Mobile and Snapdragon Wear.EPSS 0.8%CVE-2018-11935—Improper input validation might result in incorrect app id returned to the caller Instead of returning failure in Snapdragon Auto, SnapdragoEPSS 0.8%CVE-2020-11279HIGHMemory corruption while processing crafted SDES packets due to improper length check in sdes packets recieved in Snapdragon Auto, SnapdragonEPSS 0.8%CVE-2019-2334—Null pointer dereferencing can happen when playing the clip with wrong block group id in Snapdragon Auto, Snapdragon Compute, Snapdragon ConEPSS 0.8%CVE-2018-11955—Lack of check on length of reason-code fetched from payload may lead driver access the memory not allocated to the frame and results in out EPSS 0.8%CVE-2019-10591—Null pointer dereference can happen when parsing udta atom which is non-standard and having invalid depth in Snapdragon Auto, Snapdragon ComEPSS 0.8%CVE-2019-14022—Error occurs While extracting the ipv6_header having an invalid length due to lack of length check in Snapdragon Auto, Snapdragon Compute, SEPSS 0.8%CVE-2020-11292HIGHPossible buffer overflow in voice service due to lack of input validation of parameters in QMI Voice API in Snapdragon Auto, Snapdragon CompEPSS 0.8%CVE-2019-14012—Possibility of null pointer deference as the array of video codecs from media info is referenced without null checking while processing SDP EPSS 0.8%CVE-2019-14061—Null-pointer dereference can occur while accessing the segment element info when it is not allocated and assigned in Snapdragon Auto, SnapdrEPSS 0.8%CVE-2019-10578—Null pointer dereference can occur while parsing the clip which is nonstandard in Snapdragon Auto, Snapdragon Compute, Snapdragon ConnectiviEPSS 0.8%CVE-2019-10549—Null pointer dereference issue can happen due to improper validation of CSEQ header response received from network in Snapdragon Auto, SnapdEPSS 0.8%CVE-2019-10489—Possible null-pointer dereference can occur while parsing avi clip during copy in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IEPSS 0.8%CVE-2019-14003—Null pointer exception can happen while parsing invalid MKV clip where cue information is parsed before segment information in Snapdragon AuEPSS 0.8%CVE-2019-14008—Possible null pointer dereference issue in location assistance data processing due to missing null check on resources before using it in SnaEPSS 0.8%CVE-2016-10415—In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9640, MDEPSS 0.8%CVE-2020-11218—Denial of service in baseband when NW configures LTE betaOffset-RI-Index due to lack of data validation in Snapdragon Auto, Snapdragon CompuEPSS 0.8%CVE-2015-9140—In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile, Snapdragon Wear, and Small Cell SoC FSM9055, MDMEPSS 0.8%