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-2019-2320—Possible out of bounds write in a MT SMS/SS scenario due to improper validation of array index in Snapdragon Auto, Snapdragon Compute, SnapdEPSS 0.9%CVE-2019-10590—Out of bound access while parsing dts atom, which is non-standard as it does not have valid number of tracks in Snapdragon Auto, Snapdragon EPSS 0.9%CVE-2019-10541—Dereference on uninitialized buffer can happen when parsing FLV clip with corrupted codec specific data in Snapdragon Auto, Snapdragon CompuEPSS 0.9%CVE-2019-10493—Position determination accuracy may be degraded due to wrongly decoded information in Snapdragon Auto, Snapdragon Compute, Snapdragon ConsumEPSS 0.9%CVE-2019-10516—Multiple read overflows in MM while decoding service accept,service reject,attach reject and MT detach in Snapdragon Auto, Snapdragon ComputEPSS 0.9%CVE-2020-3639—u'When a non standard SIP sigcomp message is received from the network, then there may be chances of using more UDVM cycle or memory overfloEPSS 0.9%CVE-2019-10589—Lack of length check of response buffer can lead to buffer over-flow while GP command response buffer handling in Snapdragon Auto, SnapdragoEPSS 0.9%CVE-2019-2294—Usage of hard-coded magic number for calculating heap guard bytes can allow users to corrupt heap blocks without heap algorithm knowledge inEPSS 0.9%CVE-2019-2258—Improper validation of array index causes OOB write and then leads to memory corruption in MMCP in Snapdragon Auto, Snapdragon Compute, SnapEPSS 0.9%CVE-2019-2332—Memory corruption while accessing the memory as payload size is not validated before access in Snapdragon Auto, Snapdragon Compute, SnapdragEPSS 0.9%CVE-2019-10614—Out of boundary access is possible as there is no validation of data accessed against the received size of the packet in case of malicious fEPSS 0.9%CVE-2019-2322—Buffer overflow can occur when playing specific clip which is non-standard in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, EPSS 0.9%CVE-2019-14111—Possible buffer overflow while handling NAN reception of NMF in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon ConEPSS 0.9%CVE-2019-10539—Possible buffer overflow issue due to lack of length check when parsing the extended cap IE header length in Snapdragon Auto, Snapdragon ComEPSS 0.9%CVE-2019-14017—Heap buffer overflow can occur while parsing invalid MKV clip which is not standard and have invalid vorbis codec data in Snapdragon Auto, SEPSS 0.9%CVE-2019-10593—Buffer overflow can occur when processing non standard SDP video Image attribute parameter in a VILTE\VOLTE call in Snapdragon Auto, SnapdraEPSS 0.9%CVE-2019-14004—Buffer overflow occurs while processing invalid MKV clip, which has invalid EBML size in Snapdragon Auto, Snapdragon Compute, Snapdragon ConEPSS 0.9%CVE-2020-3661—Buffer overflow will happen while parsing mp4 clip with corrupted sample atoms values which exceeds MAX_UINT32 range due to lack of validatiEPSS 0.9%CVE-2019-2300—Possible buffer overflow in WLAN handler due to lack of validation of destination buffer size before copying into it in Snapdragon Auto, SnaEPSS 0.9%CVE-2019-10594—Stack overflow can occur when SDP is received with multiple payload types in the FMTP attribute of a video M line in Snapdragon Auto, SnapdrEPSS 0.9%