Slonser

A heap buffer overflow exists in ANGLE, a graphics abstraction layer, within Google Chrome on Mac. This issue allows a remote attacker to perform out-of-bounds memory access by inducing the browser to process a specially crafted HTML page.

An out-of-bounds read exists in ANGLE, a graphics abstraction layer. A remote attacker who has already compromised the renderer process can use a specially crafted HTML page to read potentially sensitive information from the process memory.

A side-channel information leakage issue exists in the Scroll component. This flaw allows a remote attacker to leak cross-origin data, which is data belonging to a different origin than the one serving the malicious page, by using a specially crafted HTML page.

The issue is related to a spoofing vulnerability in Microsoft Exchange Server, which allows attackers to affect the system. This vulnerability can be exploited to conduct spoofing attacks, making an attacker's email address appear legitimate to the victim. The vulnerability is caused by the current implementation of the P2 FROM header verification. It is particularly useful for spear phishing and other forms of email-based deception. Over 1 million potential targets have been found.

The issue is related to the `readCodeFor` function in the mysql2 package, which is vulnerable to Remote Code Execution (RCE) due to improper validation of the `supportBigNumbers` and `bigNumberStrings` values. This allows a remote attacker to execute arbitrary code.

The issue is related to Improper Input Validation through the `keyFromFields` function, resulting in cache poisoning. An attacker can inject a colon `:` character within a value of the attacker-crafted key.

The issue allows for Information Exposure when the style attribute is permitted on the backend, enabling an attacker to enumerate files in the system, including project dependencies. This could be exploited to gather details about the file system structure and dependencies of the targeted server.

The issue is related to the ParseAddressList function, which incorrectly handles comments within display names. This can lead to different trust decisions being made by programs using different parsers, potentially allowing a remote attacker to perform spoofing attacks by providing specially crafted input data.

The issue is related to an inappropriate implementation in the Payments component of Google Chrome, allowing a remote attacker to bypass XSS preventions via a malicious file. This can enable the attacker to circumvent security restrictions and gain unauthorized access to protected information. The Chromium security severity of this issue is rated as High.