Jason Villaluna

An inappropriate implementation in the Safe Browsing component allows a remote attacker to bypass navigation restrictions by using a specially crafted HTML page.

A use after free issue exists in the Import component. This occurs when a remote attacker convinces a user to perform specific UI gestures, potentially leading to arbitrary code execution through a malicious file. Use after free is a memory corruption flaw where the program continues to use a pointer after it has been freed.

A use after free issue in Chromoting allows a remote attacker to execute arbitrary code through malicious network traffic. Use after free is a memory corruption flaw that occurs when an application continues to use a pointer after it has been freed.

A use after free issue exists in Views, which allows a remote attacker to execute arbitrary code. This is achieved by convincing a user to perform specific UI gestures while interacting with a crafted HTML page. Use after free is a memory corruption flaw that occurs when an application continues to use a pointer after it has been freed.

A type confusion issue exists in Chrome Tabs. This flaw allows a remote attacker who has already compromised the renderer process to potentially achieve a sandbox escape by using a specially crafted HTML page. Type confusion occurs when a program allocates a resource as one type but accesses it as another, potentially leading to memory corruption or unauthorized code execution.

An out of bounds read in ANGLE allows a remote attacker to obtain potentially sensitive information from process memory by using a crafted HTML page. ANGLE (Almost Native Graphics Layer Engine) is a compatibility layer that allows OpenGL ES APIs to run on top of other graphics APIs.

Insufficient validation of untrusted input in Enterprise allows a remote attacker to perform UI spoofing via a crafted HTML page. UI spoofing is a technique where an attacker mimics a legitimate user interface to deceive users into performing unintended actions.

Name of the Vulnerable Software and Affected Versions: Apache ORC versions 1.8.0 through 1.8.8 Apache ORC versions 1.9.0 through 1.9.5 Apache ORC versions 2.0.0 through 2.0.4 Apache ORC versions 2.1.0 through 2.1.1 Description: A Heap-based Buffer Overflow vulnerability has been identified in the ORC C++ LZO decompression logic. Specially crafted malformed ORC files can cause the decompressor to allocate a 250-byte buffer but then attempt to copy 295 bytes into it, resulting in memory corruption. Recommendations: For Apache ORC versions 1.8.0 through 1.8.8, upgrade to version 1.8.9. For Apache ORC versions 1.9.0 through 1.9.5, upgrade to version 1.9.6. For Apache ORC versions 2.0.0 through 2.0.4, upgrade to version 2.0.5. For Apache ORC versions 2.1.0 through 2.1.1, upgrade to version 2.1.2.