CVE-2018-6132 – chromium-browser: Use of uninitialized memory in WebRTC
https://notcve.org/view.php?id=CVE-2018-6132
Uninitialized data in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted video file. Los datos no inicializados en WebRTC en Google Chrome antes de 67.0.3396.62 permitieron a un atacante remoto obtener información potencialmente sensible de la memoria de proceso a través de un archivo de video creado. • https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://crbug.com/839960 https://access.redhat.com/security/cve/CVE-2018-6132 https://bugzilla.redhat.com/show_bug.cgi?id=1584043 • CWE-908: Use of Uninitialized Resource •
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-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 •