CVE-2018-6123 – chromium-browser: Use after free in Blink
https://notcve.org/view.php?id=CVE-2018-6123
A use after free in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. Un uso de memoria previamente liberada en Blink en Google Chrome, en versiones anteriores a la 67.0.3396.62, permitía que un atacante remoto pudiese explotar una corrupción de memoria dinámica (heap) mediante una página HTML manipulada. • http://www.securityfocus.com/bid/104309 http://www.securitytracker.com/id/1041014 https://access.redhat.com/errata/RHSA-2018:1815 https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://crbug.com/835639 https://www.debian.org/security/2018/dsa-4237 https://access.redhat.com/security/cve/CVE-2018-6123 https://bugzilla.redhat.com/show_bug.cgi?id=1584032 • CWE-416: Use After Free CWE-787: Out-of-bounds Write •
CVE-2018-6137 – chromium-browser: Leak of visited status of page in Blink
https://notcve.org/view.php?id=CVE-2018-6137
CSS Paint API in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to leak cross-origin data via a crafted HTML page. La API CSS Paint en Blink en Google Chrome, en versiones anteriores a la 67.0.3396.62, permitía que un atacante remoto filtrase los datos cross-origin mediante una página HTML manipulada. • http://www.securityfocus.com/bid/104309 http://www.securitytracker.com/id/1041014 https://access.redhat.com/errata/RHSA-2018:1815 https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://crbug.com/835589 https://www.debian.org/security/2018/dsa-4237 https://access.redhat.com/security/cve/CVE-2018-6137 https://bugzilla.redhat.com/show_bug.cgi?id=1584048 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVE-2018-6139 – chromium-browser: Restrictions bypass in the debugger extension API
https://notcve.org/view.php?id=CVE-2018-6139
Insufficient target checks on the chrome.debugger API in DevTools in Google Chrome prior to 67.0.3396.62 allowed an attacker who convinced a user to install a malicious extension to execute arbitrary code via a crafted Chrome Extension. Las comprobaciones de destino insuficientes en la API chrome.debugger en DevTools en Google Chrome, en versiones anteriores a la 67.0.3396.62, permitía que un atacante, que hubiese convencido a un usuario para que instale una extensión maliciosa, ejecute código arbitrario mediante una extensión de Chrome manipulada. • http://www.securityfocus.com/bid/104309 http://www.securitytracker.com/id/1041014 https://access.redhat.com/errata/RHSA-2018:1815 https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://crbug.com/805224 https://www.debian.org/security/2018/dsa-4237 https://access.redhat.com/security/cve/CVE-2018-6139 https://bugzilla.redhat.com/show_bug.cgi?id=1584050 • CWE-20: Improper Input Validation •
CVE-2018-6140 – chromium-browser: Restrictions bypass in the debugger extension API
https://notcve.org/view.php?id=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 convinced a user to install a malicious extension to execute arbitrary code via a crafted Chrome Extension. Permitir que la API chrome.debugger se adjunte en las páginas de Web UI en DevTools en Google Chrome en versiones anteriores a la 67.0.3396.62 permitía que un atacante que hubiese convencido a un usuario para que instale una extensión maliciosa ejecute código arbitrario mediante una extensión de Chrome manipulada. • http://www.securityfocus.com/bid/104309 http://www.securitytracker.com/id/1041014 https://access.redhat.com/errata/RHSA-2018:1815 https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://crbug.com/798222 https://www.debian.org/security/2018/dsa-4237 https://access.redhat.com/security/cve/CVE-2018-6140 https://bugzilla.redhat.com/show_bug.cgi?id=1584051 • CWE-20: Improper Input Validation •
CVE-2018-6129 – WebRTC - VP9 Missing Frame Processing Out-of-Bounds Memory Access
https://notcve.org/view.php?id=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 memory access via a crafted HTML page. El acceso a la matriz fuera de límites en WebRTC en Google Chrome antes de 67.0.3396.62 permitió que un atacante remoto pudiera realizar un acceso a la memoria fuera de límites a través de una página HTML diseñada. WebRTC VP9 missing frame processing suffers from an out-of-bounds memory access vulnerability. • https://www.exploit-db.com/exploits/44863 https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://crbug.com/838672 https://access.redhat.com/security/cve/CVE-2018-6129 https://bugzilla.redhat.com/show_bug.cgi?id=1584039 • CWE-125: Out-of-bounds Read •