Youngjoo Lee

**Name of the Vulnerable Software and Affected Versions** Google Chrome versions prior to 103.0.5060.134 Microsoft Edge (affected versions not specified) **Description** The issue is related to a use after free in the Views component, which can lead to heap corruption via UI interaction. A remote attacker who convinces a user to engage in specific interactions can potentially exploit this issue. The estimated number of potentially affected devices worldwide is not specified. There is no information about real-world incidents where this issue was exploited. **Recommendations** For Google Chrome versions prior to 103.0.5060.134, update to version 103.0.5060.134 or later to resolve the issue. For Microsoft Edge, at the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Google Chrome versions prior to 87.0.4280.141 **Description** The issue is related to a use after free vulnerability in the Blink module of Google Chrome, which can be exploited by a remote attacker to potentially corrupt the heap via a crafted HTML page. This could impact the confidentiality, integrity, and availability of protected information. **Recommendations** For versions prior to 87.0.4280.141, update to version 87.0.4280.141 or later to resolve the issue. As a temporary workaround, consider restricting access to potentially malicious HTML pages until the update is applied.

**Name of the Vulnerable Software and Affected Versions** Google Chrome versions prior to 86.0.4240.75 **Description** The issue is related to a use after free in WebXR, which can potentially lead to heap corruption. A remote attacker could exploit this via a crafted HTML page. The vulnerability is also described as a buffer overflow in memory related to the WebVR API, allowing a remote attacker to bypass existing security restrictions. **Recommendations** For versions prior to 86.0.4240.75, update to version 86.0.4240.75 or later to resolve the issue. As a temporary workaround, consider restricting access to WebXR and WebVR APIs until the update is applied. Avoid using crafted HTML pages that could exploit the heap corruption via the vulnerable WebXR component.