Luan Herrera

A UI misrepresentation issue exists in the FileAPI. A remote attacker can use social engineering and a specially crafted HTML page to spoof UI elements.

An inappropriate implementation in the Autofill feature allows a remote attacker who has already compromised the renderer process to leak cross-origin data. This is achieved by using a specially crafted HTML page.

Insufficient policy enforcement in the IFrame Sandbox allows a remote attacker to bypass navigation restrictions by using a crafted HTML page.

Insufficient policy enforcement in Isolated Web Apps allows a remote attacker to bypass the content security policy (CSP), which is a security layer used to detect and mitigate certain types of attacks, such as cross-site scripting, by restricting the resources that a browser is allowed to load. This bypass can be achieved through the use of a crafted HTML page.

An issue in the Background Fetch API in Google Chrome allowed a remote attacker to leak cross-origin data through a specially crafted HTML page. The security severity is rated as High.

Name of the Vulnerable Software and Affected Versions Google Chrome versions prior to 147.0.7727.55 Description A policy bypass issue existed in the Downloads component of Google Chrome. This allowed a remote attacker to circumvent multi-download protections through a specially crafted HTML page. Recommendations Update Google Chrome to version 147.0.7727.55 or later.

A race condition in WebAppInstalls allows a remote attacker to spoof UI elements by using a crafted HTML page. A race condition occurs when the timing or sequence of events is unplanned, leading to unexpected behavior.

A flaw exists in Google Chrome due to insufficient policy enforcement in Frames. This allows a remote attacker to perform UI spoofing using a specially crafted HTML page. The Chromium security severity is rated as Medium.

Name of the Vulnerable Software and Affected Versions: Firefox versions prior to 127 Firefox ESR versions prior to 115.12 Thunderbird versions prior to 115.12 Description: The issue is related to security setting errors in Mozilla browsers, allowing a remote attacker to bypass security restrictions and conduct a clickjacking attack. By exploiting this, a sandboxed iframe could present a button that, if clicked by a user, would bypass restrictions to open a new window, potentially tricking the browser with a `X-Frame-Options` header. Recommendations: For Firefox versions prior to 127, update to version 127 or later to resolve the issue. For Firefox ESR versions prior to 115.12, update to version 115.12 or later to resolve the issue. For Thunderbird versions prior to 115.12, update to version 115.12 or later to resolve the issue.

The issue was addressed with improved checks. Processing web content may disclose sensitive information.

The issue is related to an inappropriate implementation in WebApp Installs, allowing a remote attacker to potentially spoof the contents of the Omnibox (URL bar) via a crafted HTML page. This could lead to the attacker gaining access to confidential information.

Name of the Vulnerable Software and Affected Versions Google Chrome versions prior to 147.0.7727.55 Description A policy bypass issue existed in Google Chrome's audio component, prior to version 147.0.7727.55. A remote attacker could bypass sandbox download restrictions by convincing a user to perform specific UI gestures on a crafted HTML page. The Chromium security severity is rated as Low. Recommendations Update Google Chrome to version 147.0.7727.55 or later.

The issue is related to insufficient validation of untrusted input in the Downloads component, allowing an attacker to bypass Downloads restrictions. This can be achieved by convincing a user to install a malicious extension via a crafted HTML page. The attacker can exploit this issue to impact data integrity.

The issue is related to a lack of proper origin confirmation, allowing navigations when dragging a URL from a cross-origin iframe into the same tab. This could lead to website spoofing attacks. The vulnerability may allow a remote attacker to impact data integrity.

The issue is related to the implementation of the Cross-Origin Resource Sharing (CORS) mechanism in browsers, which allows a malicious website to learn the size of a cross-origin resource that supports Range requests. This can be achieved by exploiting the vulnerability with a specially crafted request containing a Range header.

The issue is related to errors in processing HTML content. It may allow a remote attacker to execute arbitrary code using a specially crafted web page. Memory safety bugs have been reported, showing evidence of memory corruption, which could potentially be exploited to run arbitrary code.

The issue is related to how error messages are handled when importing resources using Web Workers, potentially allowing an attacker to distinguish between `application/javascript` responses and non-script responses, and thus learn information cross-origin. This could be abused to gain unauthorized access to protected information.

The issue is related to an inappropriate implementation in Blink, allowing a remote attacker to leak cross-origin data via a crafted HTML page. This is due to a lack of proper source data validation, enabling an attacker to disclose protected information using a specially designed HTML page.

The issue is related to an inappropriate implementation in Navigation, allowing a remote attacker to leak cross-origin data via a crafted HTML page. This could potentially reveal protected information. The problem is associated with improperly implemented security checks for standard elements.

The issue is related to insufficient data validation in the loader, allowing a remote attacker to leak cross-origin data via a crafted HTML page. This could potentially lead to the disclosure of protected information.