Sergei Glazunov

A heap use-after-free vulnerability exists in libxml2 and libxslt due to improper handling of attribute types, specifically the `atype` flags. This flaw occurs when processing certain XSLT operations, leading to memory corruption. Exploitation can result in crashes or potentially allow an attacker to execute arbitrary code. The vulnerability impacts various systems, including AWS Lambda base images and Oracle Linux.

The issue is related to a use after free vulnerability in the Navigation component of Google Chrome and Microsoft Edge browsers. This vulnerability can be exploited by a remote attacker using a specially crafted HTML page, potentially allowing the execution of arbitrary code. The severity of this issue is considered high.

The issue is related to an out of bounds memory access in V8, allowing a remote attacker to perform an out of bounds memory read via a crafted HTML page. This can potentially impact the confidentiality, integrity, and availability of protected information.

The issue is related to type confusion in V8, a JavaScript engine used by Google Chrome, allowing a remote attacker to potentially exploit heap corruption via a crafted HTML page. This could lead to arbitrary code execution. The severity of this issue is classified as High by Chromium security.

The issue is related to an out of bounds memory access in V8, a component of Google Chrome, which could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page. The severity of this issue is classified as High by Chromium security.

The issue is related to a use after free vulnerability in the WebXR component of Google Chrome, which can lead to heap corruption. This can potentially allow a remote attacker to execute arbitrary code via a crafted HTML page.

The issue is related to a type confusion in the V8 JavaScript engine, allowing a remote attacker to potentially exploit heap corruption via a crafted HTML page. This could lead to a denial of service or the execution of arbitrary code. The estimated number of potentially affected devices is not specified.

The issue is related to a type confusion in the V8 JavaScript engine, allowing a remote attacker to potentially exploit heap corruption via a crafted HTML page. This could lead to a denial of service or the execution of arbitrary code. The severity of this issue is classified as High by Chromium.

The issue is related to type confusion in the V8 JavaScript engine, allowing a remote attacker to potentially exploit heap corruption via a crafted HTML page. This could impact the confidentiality, integrity, and availability of protected information.

The issue is related to a heap buffer overflow in the UMA (User Metrics Analysis) component of Google Chrome when processing HTML content. This can be exploited by a remote attacker using a specially crafted HTML page, potentially compromising the confidentiality, integrity, and availability of protected information.

A heap buffer overflow issue in the Metrics component of Google Chrome allows a remote attacker who has compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. This could impact the confidentiality, integrity, and availability of protected information.

The issue is related to an inappropriate implementation in Blink, allowing a remote attacker to perform arbitrary read/write via a crafted HTML page. This is due to a use-after-free vulnerability in the page display mechanism. The estimated number of potentially affected devices worldwide is not specified. There is no information about real-world incidents where this issue was exploited.

The issue is related to a use after free in the Layout component, which could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page. The severity of this issue is considered high.

The issue is related to a use after free in the Audio component, allowing an attacker to potentially exploit heap corruption via a crafted Chrome Extension. This could be achieved if the attacker convinces a user to install a malicious extension. The exploitation of this issue may allow a remote attacker to access confidential data, compromise its integrity, and cause a denial of service.

The issue is related to a use after free vulnerability in the Mojo component of Google Chrome and Microsoft Edge browsers. This vulnerability allows a remote attacker to access confidential data, compromise data integrity, and cause a denial of service using a specially crafted HTML page. The exploitation of this issue can potentially lead to heap corruption via a crafted HTML page, especially if the renderer process has been compromised.

The issue is related to a use after free in Passwords, allowing a remote attacker who has compromised the renderer process to potentially exploit heap corruption via a crafted HTML page.

The issue is related to a use-after-free vulnerability in the Network Service of Google Chrome and Microsoft Edge browsers. This vulnerability can be exploited by a remote attacker to potentially execute arbitrary code via heap corruption using a crafted HTML page.

A use after free in FedCM allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. The vulnerability is related to the use of memory after it has been freed, which could allow a remote attacker to execute arbitrary code. The issue is associated with the Federated Credential Management (FedCM) API, which enables the creation of unified identity services that preserve privacy and work without cross-site tracking mechanisms, such as third-party cookie handling.

The issue is related to a use after free in Browser Creation, which could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page if the user engages in a specific UI interaction. This could lead to arbitrary code execution.

The issue is related to a heap buffer overflow in the Downloads function of the browsers, which can be exploited by a remote attacker using a specially crafted web page. This could potentially allow the execution of arbitrary code. The estimated number of potentially affected devices is not specified.