CVE-2018-6127 – chromium-browser: Use after free in indexedDB
https://notcve.org/view.php?id=CVE-2018-6127
Early free of object in use in IndexDB in Google Chrome prior to 67.0.3396.62 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. La liberación temprana del objeto en uso en IndexDB en Google Chrome, en versiones anteriores a la 67.0.3396.62, permitía que un atacante remoto, que hubiese comprometido el proceso renderer, pudiese realizar una escritura de memoria fuera de límites 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/842990 https://www.debian.org/security/2018/dsa-4237 https://access.redhat.com/security/cve/CVE-2018-6127 https://bugzilla.redhat.com/show_bug.cgi?id=1584037 • CWE-416: Use After Free •
CVE-2018-6131 – chromium-browser: Incorrect mutability protection in WebAssembly
https://notcve.org/view.php?id=CVE-2018-6131
Object lifecycle issue in WebAssembly in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. El problema del lifecycle del objeto en WebAssembly en Google Chrome antes de 67.0.3396.62 permitía a un atacante remoto explotar potencialmente la corrupción del montón a través de una página HTML diseñada. • https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://crbug.com/826434 https://access.redhat.com/security/cve/CVE-2018-6131 https://bugzilla.redhat.com/show_bug.cgi?id=1584042 • CWE-787: Out-of-bounds Write •
CVE-2018-6147 – chromium-browser: Password fields not taking advantage of OS protections in Views
https://notcve.org/view.php?id=CVE-2018-6147
Lack of secure text entry mode in Browser UI in Google Chrome on Mac prior to 67.0.3396.62 allowed a local attacker to obtain potentially sensitive information from process memory via a local process. La falta de un modo seguro de introducción de texto en Browser UI en Google Chrome, en versiones anteriores a la 67.0.3396.62, permitía que un atacante local pudiese obtener información potencialmente sensible del la memoria del proceso mediante un proceso local. • 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/818133 https://www.debian.org/security/2018/dsa-4237 https://access.redhat.com/security/cve/CVE-2018-6147 https://bugzilla.redhat.com/show_bug.cgi?id=1584058 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
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 •
CVE-2018-6130 – WebRTC - VP9 Frame Processing Out-of-Bounds Memory Access
https://notcve.org/view.php?id=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 out of bounds memory access via a crafted HTML page. El manejo incorrecto de la vida útil de los objetos 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 frame processing a suffers from an out-of-bounds memory access vulnerability. • https://www.exploit-db.com/exploits/44862 https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://crbug.com/838402 https://access.redhat.com/security/cve/CVE-2018-6130 https://bugzilla.redhat.com/show_bug.cgi?id=1584040 • CWE-125: Out-of-bounds Read •