Vulnerabilidades em google
7.003 resultadosAnálise Vexday
Google registra presença mínima no panorama de risco com apenas 4 vulnerabilidades na base, nenhuma sob exploração ativa (KEV) e apenas 1 crítica identificada. A fraqueza dominante relaciona-se a validação inadequada de entrada (CWE-20), indicando risco controlado e sem pressão temporal dado que não há publicações nos últimos 90 dias.
CVE-2024-47027HIGHIn sm_mem_compat_get_vmm_obj of lib/sm/shared_mem.c, there is a possible arbitrary physical memory access due to improper input validation. EPSS 0.1%CVE-2023-21245HIGHIn showNextSecurityScreenOrFinish of KeyguardSecurityContainerController.java, there is a possible way to access the lock screen during deviEPSS 0.1%CVE-2023-21379—In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure in the BEPSS 0.1%CVE-2025-48588HIGHIn startAlwaysOnVpn of Vpn.java, there is a possible way to disable always-on VPN due to a logic error in the code. This could lead to localEPSS 0.1%CVE-2023-21271—In parseInputs of ShimPreparedModel.cpp, there is a possible out of bounds read due to improper input validation. This could lead to local iEPSS 0.1%CVE-2024-25986HIGHIn ppmp_unprotect_buf of drm_fw.c, there is a possible compromise of protected memory due to a logic error in the code. This could lead to lEPSS 0.1%CVE-2023-21320—In Device Policy, there is a possible way to verify if a particular admin app is registered on the device due to side channel information diEPSS 0.1%CVE-2024-27209HIGHthere is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional eEPSS 0.1%CVE-2023-21307—In Bluetooth, there is a possible way for a paired Bluetooth device to access a long term identifier for an Android device due to a permissiEPSS 0.1%CVE-2023-21360—In Bluetooth, there is a possible out of bounds write due to improper input validation. This could lead to local escalation of privilege witEPSS 0.1%CVE-2026-45525LOWIn multiple locations, there is a possible improper data sanitization due to a logic error in the code. This could lead to local informationEPSS 0.1%CVE-2026-28581MEDIUMIn fixInitiatingUserIfNecessary of CallIntentProcessor.java, there is a possible way to make an emergency call due to a logic error in the cEPSS 0.1%CVE-2025-26444HIGHIn onHandleForceStop of VoiceInteractionManagerService.java, there is a bug that could cause the system to incorrectly revert to the defaultEPSS 0.1%CVE-2026-28638LOWIn multiple functions of XmpDataParser.java, there is a possible improper data sanitization due to a logic error in the code. This could leaEPSS 0.1%CVE-2025-48537HIGHIn multiple locations, there is a possible way to persistently DoS the device due to improper input validation. This could lead to local infEPSS 0.1%CVE-2026-28660LOWIn getAllSessions of multiple files, there is a possible confused deputy due to a logic error in the code. This could lead to local informatEPSS 0.1%CVE-2024-29752HIGHIn tmu_set_tr_num_thresholds of tmu.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalEPSS 0.1%CVE-2023-21376MEDIUMIn Telephony, there is a possible way to retrieve the ICCID due to a logic error in the code. This could lead to local information disclosurEPSS 0.1%CVE-2018-9371HIGHIn the Mediatek Preloader, there are out of bounds reads and writes due to an exposed interface that allows arbitrary peripheral memory mappEPSS 0.1%CVE-2025-22427HIGHIn onCreate of NotificationAccessConfirmationActivity.java, there is a possible way to grant notification access above the lock screen due tEPSS 0.1%