Ned Williamson

An integer overflow issue was addressed through improved input validation. Processing maliciously crafted web content may lead to an unexpected process crash.

The issue is related to a use after free in WebRTC, allowing a remote attacker to potentially exploit heap corruption via a crafted HTML page. This could impact the confidentiality, integrity, and availability of data.

The issue is related to multiple memory corruption problems, including a buffer overflow in the libxml2 library, which can be exploited by a remote attacker to cause a denial of service. The problem was addressed with improved input validation.

A use after free issue was addressed with improved memory management. This issue may allow an app to execute arbitrary code with kernel privileges.

An issue was discovered in libxml2 where certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be provoked, which may allow a remote attacker to cause a denial of service. The vulnerability is related to the handling of objects with a dict structure, where the value of the first byte is zero. This issue can be exploited by a remote attacker to cause a denial of service.

A use after free issue was addressed with improved memory management. This issue allows an application to potentially execute arbitrary code with kernel privileges.

A buffer overflow issue was addressed with improved memory handling. An attacker in a privileged network position may be able to execute arbitrary code.

A memory corruption issue was addressed with improved memory handling, allowing an application to potentially execute arbitrary code with kernel privileges.

A memory corruption issue was addressed with improved memory handling, allowing an application to potentially execute arbitrary code with kernel privileges.

A buffer overflow issue was addressed through improved size validation. This could allow a remote attacker to cause unexpected system termination or corrupt kernel memory.

A memory corruption issue was addressed with improved memory handling, which could allow a local user to read kernel memory.

A type confusion issue was addressed with improved memory handling. This issue may allow an application to cause unexpected system termination or write kernel memory.

A use-after-free issue was addressed with improved memory management. This issue allows a malicious application to execute arbitrary code with system privileges. The vulnerability is related to memory management and can be exploited by a malicious application.

A memory corruption issue was addressed with improved input validation. A malicious application may be able to execute arbitrary code with kernel privileges.

The issue is related to incorrect reference counting in the AppCache component of the Google Chrome web browser, which is associated with errors in access control for the isolated environment. Exploitation of this issue may allow a remote attacker to escape the sandbox and execute arbitrary code via a crafted HTML page.

The issue allows a remote attacker to execute arbitrary code via a crafted HTML page due to the re-entry of a destructor in the Networking Disk Cache.

A double-eviction in the Incognito mode cache led to a user-after-free in the Networking Disk Cache, allowing a remote attacker to execute arbitrary code via a crafted HTML page.

The issue is related to incorrect IPC serialization in Skia, which allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

The issue is related to a heap buffer overflow in the Blob API, which can be exploited by a remote attacker using a crafted HTML page, potentially leading to heap corruption. This is also known as a Blink out-of-bounds read.

The issue is related to an out-of-bounds write in the QUIC networking stack, allowing a remote attacker to gain code execution via a malicious server.