Vulnerabilities in google

6,565 results
Vexday analysis

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-2018-6130—Incorrect handling of object lifetimes in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially perform outEPSS 2.7%CVE-2018-6129—Out of bounds array access in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially perform out of bounds mEPSS 2.7%CVE-2021-21156—Heap buffer overflow in V8 in Google Chrome prior to 88.0.4324.182 allowed a remote attacker to potentially exploit heap corruption via a crEPSS 2.7%CVE-2019-5762—Inappropriate memory management when caching in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute arbitraryEPSS 2.7%CVE-2019-5756—Inappropriate memory management when caching in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute arbitraryEPSS 2.7%CVE-2020-6520—Buffer overflow in Skia in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit heap corruption via a crafteEPSS 2.7%CVE-2020-6449—Use after free in audio in Google Chrome prior to 80.0.3987.149 allowed a remote attacker to potentially exploit heap corruption via a craftEPSS 2.7%CVE-2020-6402—Insufficient policy enforcement in downloads in Google Chrome on OS X prior to 80.0.3987.87 allowed an attacker who convinced a user to instEPSS 2.7%CVE-2018-6101—A lack of host validation in DevTools in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to execute arbitrary code via a crafEPSS 2.7%CVE-2018-18342—Execution of user supplied Javascript during object deserialization can update object length leading to an out of bounds write in V8 in GoogEPSS 2.7%CVE-2018-6140—Allowing the chrome.debugger API to attach to Web UI pages in DevTools in Google Chrome prior to 67.0.3396.62 allowed an attacker who convinEPSS 2.6%CVE-2025-1550HIGHArbitrary Code Execution via Crafted Keras Config for Model LoadingEPSS 2.6%CVE-2020-6405—Out of bounds read in SQLite in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to obtain potentially sensitive information frEPSS 2.6%CVE-2023-35674HIGHIn onCreate of WindowState.java, there is a possible way to launch a background activity due to a logic error in the code. This could lead tEPSS 2.6%KEVCVE-2020-6548—Heap buffer overflow in Skia in Google Chrome prior to 84.0.4147.125 allowed a remote attacker who had compromised the renderer process to pEPSS 2.6%CVE-2019-5779—Insufficient policy validation in ServiceWorker in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to bypass navigation restriEPSS 2.6%CVE-2018-6111—An object lifetime issue in the developer tools network handler in Google Chrome prior to 66.0.3359.117 allowed a local attacker to execute EPSS 2.6%CVE-2024-1939HIGHType Confusion in V8 in Google Chrome prior to 122.0.6261.94 allowed a remote attacker to potentially exploit heap corruption via a crafted EPSS 2.6%CVE-2020-16012—Side-channel information leakage in graphics in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to leak cross-origin data via EPSS 2.6%CVE-2020-6518—Use after free in developer tools in Google Chrome prior to 84.0.4147.89 allowed a remote attacker who had convinced the user to use developEPSS 2.6%