Vulnerabilidades en Google Inc.

960 resultados
Análisis Vexday

Com 960 CVEs catalogadas e nenhuma entrada no catálogo KEV da CISA, o perfil de exploração ativa do Google Inc. está abaixo da média geral do catálogo, o que sugere menor pressão imediata de ataques em curso. Apesar da ausência de severidades críticas e de novas vulnerabilidades nos últimos 90 dias, há 16 CVEs com prova de conceito pública disponível, o que representa um vetor de risco concreto para equipes que ainda não aplicaram as correções correspondentes. A falha mais recorrente é CWE-269 (gerenciamento inadequado de privilégios), padrão que tipicamente favorece escalonamento de privilégios e movimentação lateral em ambientes comprometidos. A CVE mais perigosa atualmente rastreada é CVE-2017-0561, com EPSS de 0,30, indicando probabilidade não negligenciável de exploração e justificando atenção prioritária mesmo tratando-se de uma vulnerabilidade mais antiga.

CVE-2017-0474—A remote code execution vulnerability in Mediaserver could enable an attacker using a specially crafted file to cause memory corruption duriEPSS 2.1%CVE-2017-0432—An elevation of privilege vulnerability in the MediaTek driver could enable a local malicious application to execute arbitrary code within tEPSS 2.1%CVE-2017-0782—A remote code execution vulnerability in the Android system (bluetooth). Product: Android. Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7EPSS 2.1%CVE-2017-13283—In avrc_ctrl_pars_vendor_rsp of bluetooth avrcp_ctrl, there is a possible out of bounds write on the stack due to a missing bounds check. ThEPSS 2.1%CVE-2017-0582—An elevation of privilege vulnerability in the HTC OEM fastboot command could enable a local malicious application to execute arbitrary codeEPSS 2.1%CVE-2018-9446—In smp_br_state_machine_event of smp_br_main.cc, there is a possible out of bounds write due to memory corruption. This could lead to remoteEPSS 2.1%CVE-2017-0553—An elevation of privilege vulnerability in libnl could enable a local malicious application to execute arbitrary code within the context of EPSS 2.0%CVE-2018-9556—In ParsePayloadHeader of payload_metadata.cc, there is a possible out of bounds write due to an integer overflow. This could lead to remote EPSS 2.0%CVE-2017-13230—In hevc codec, there is an out-of-bounds write due to an incorrect bounds check with the i2_pic_width_in_luma_samples value. This could leadEPSS 1.9%CVE-2017-0406—A remote code execution vulnerability in Mediaserver could enable an attacker using a specially crafted file to cause memory corruption duriEPSS 1.9%CVE-2017-0407—A remote code execution vulnerability in Mediaserver could enable an attacker using a specially crafted file to cause memory corruption duriEPSS 1.9%CVE-2017-0807—An elevation of privilege vulnerability in the Android framework (ui framework). Product: Android. Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1EPSS 1.9%CVE-2017-0648—An elevation of privilege vulnerability in the kernel FIQ debugger could enable a local malicious application to execute arbitrary code withEPSS 1.8%CVE-2018-9427—In CopyToOMX of OMXNodeInstance.cpp there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote arbiEPSS 1.8%CVE-2017-0478—A remote code execution vulnerability in the Framesequence library could enable an attacker using a specially crafted file to execute arbitrEPSS 1.8%CVE-2017-0510—An elevation of privilege vulnerability in the kernel FIQ debugger could enable a local malicious application to execute arbitrary code withEPSS 1.8%CVE-2017-0508—An elevation of privilege vulnerability in the kernel ION subsystem could enable a local malicious application to execute arbitrary code witEPSS 1.8%CVE-2017-0507—An elevation of privilege vulnerability in the kernel ION subsystem could enable a local malicious application to execute arbitrary code witEPSS 1.8%CVE-2017-0528—An elevation of privilege vulnerability in the kernel security subsystem could enable a local malicious application to to execute code in thEPSS 1.8%CVE-2018-9496—In ixheaacd_real_synth_fft_p3 of ixheaacd_esbr_fft.c there is a possible out of bounds write due to a missing bounds check. This could lead EPSS 1.8%