Zhe Jin

The issue is related to a use after free in Blink, which can potentially allow a remote attacker to exploit heap corruption via a crafted HTML page. This could lead to unauthorized access to confidential data, disruption of data integrity, and denial of service.

The issue is related to a use after free in the media component of Google Chrome, which can be exploited by a remote attacker to access confidential data, compromise data integrity, and cause a denial of service via a specially crafted HTML page. This can potentially allow the attacker to perform a sandbox escape if the renderer process is compromised.

The issue is related to a use after free in storage, which could allow a remote attacker who has compromised the renderer process to potentially perform a sandbox escape. This can be achieved via a crafted HTML page. The exploitation of this issue may allow an attacker to access confidential data, compromise data integrity, and cause a denial of service.

The issue is related to a use after free in task scheduling, which could allow a remote attacker who has compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. This could lead to unauthorized access to confidential data, disruption of data integrity, and denial of service.

The issue is related to a use after free in the payments mechanism of Google Chrome, which can be exploited by a remote attacker via a crafted HTML page. This could potentially allow the attacker to exploit heap corruption. The exploitation of this issue may enable the attacker to access confidential data, compromise data integrity, and cause a denial of service.

The issue allows a remote attacker to potentially exploit heap corruption via a crafted HTML page, which could lead to unauthorized access to confidential data, denial of service, or impact data integrity.

The issue is related to a use after free in the audio component, which could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page. This may lead to unauthorized access to sensitive data, disruption of data integrity, and potentially cause a denial of service.

The issue is related to a use-after-free in WebSockets, which could allow a remote attacker to exploit heap corruption via a crafted HTML page. This may lead to unauthorized access to protected information and compromise its integrity and availability.

The issue is caused by multiple memory corruption problems, which can be exploited by processing maliciously crafted web content, potentially leading to arbitrary code execution. This is due to a buffer overflow in the WebKit display module, allowing a remote attacker to execute arbitrary code.

The issue is related to a use after free in the Blink rendering engine of Google Chrome, which can be exploited by a remote attacker using a specially crafted HTML page. This could potentially lead to data corruption, unauthorized access to sensitive information, and denial of service.

The issue is related to incorrect object lifecycle management in Blink, which can lead to heap corruption. A remote attacker can potentially exploit this issue via a crafted HTML page, causing a denial of service.

The issue is related to insufficient checks of pointer validity in WebRTC, allowing a remote attacker to potentially exploit heap corruption via a crafted HTML page. This could lead to a denial of service.

The issue is related to the use of memory after it has been freed in the HTMLImportsController function of the Blink rendering engine in Google Chrome. This could allow a remote attacker to potentially exploit heap corruption by using a specially crafted HTML page.

A heap buffer overflow in the GPU of Google Chrome allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. The issue is related to a buffer overflow in the GPU engine, which could be exploited by a remote attacker using a specially crafted HTML page, potentially leading to a denial of service.

The issue is caused by the incorrect, thread-unsafe use of SkImage in Canvas, which can lead to heap corruption. A remote attacker can potentially exploit this issue via a crafted HTML page, allowing them to cause buffer overflow.

The issue is related to a use after free in the WebAudio component, which could allow a remote attacker to exploit heap corruption via a crafted HTML page. This could potentially lead to a denial of service.

A race condition in the Oilpan component of Google Chrome allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. This could impact the confidentiality, integrity, and availability of protected information.

A remote code execution issue in the Android media framework's libavc library is related to inadequate access control. This allows a remote attacker to execute arbitrary code.

The issue is related to a remote code execution vulnerability in the Android media framework, specifically in the libhevc library. This vulnerability is associated with insufficient access control, which can be exploited by a remote attacker to execute arbitrary code.

The issue is related to a remote code execution vulnerability in the Android media framework, specifically in the libstagefright library. This vulnerability is associated with inadequate access control. It allows a remote attacker to execute arbitrary code.