Shhnjk

تتعلق هذه المشكلة بتسرب المعلومات في ميزة BizChat في Microsoft 365 Copilot.

يوجد ثغرة في معالجة واجهة برمجة التطبيقات (API) الخاصة بالوضع الكامل (Fullscreen) وعرض واجهة المستخدم، مما يسمح لمهاجم عن بُعد بالتقاط البيانات الحساسة التي يدخلها المستخدم، مثل بيانات اعتماد تسجيل الدخول وعناوين البريد الإلكتروني. ويتم ذلك عن طريق عرض واجهة شاشة كاملة خادعة تحتوي على عناصر تحكم مزيفة في المتصفح وعنصر تشتيت الانتباه، مثل شاشة الموافقة على ملفات تعريف الارتباط، لإخفاء إشعارات الشاشة الكاملة. ويؤدي هذا التلاعب إلى حث المستخدمين على التفاعل مع موقع ويب ضار.

The issue is related to insufficient policy enforcement in Navigation, allowing a remote attacker to leak cross-origin data via a crafted HTML page. This could potentially affect a significant number of devices worldwide, although the exact number is not specified. There is no information provided about real-world incidents where this issue was exploited.

The issue is related to an inappropriate implementation in cookies, allowing a remote attacker to bypass cookie restrictions via a crafted HTML page. This could potentially lead to unauthorized access to protected information. The vulnerability is associated with errors in the implementation of security checks for standard elements in the cookie handling mechanism of Google Chrome.

The issue is related to insufficient policy enforcement in the Blink module of Google Chrome, allowing a remote attacker to leak cross-origin data via a crafted HTML page. This could enable the attacker to access confidential data.

Name of the Vulnerable Software and Affected Versions: Safari versions prior to 11.1.2 iOS versions prior to 12 Description: An inconsistent user interface issue was addressed with improved state management. Recommendations: For Safari versions prior to 11.1.2, update to version 11.1.2 or later. For iOS versions prior to 12, update to version 12 or later.

A cross-site scripting issue existed in Safari, which was addressed with improved URL validation.

The issue concerns incorrect handling of the googlechrome:// URL scheme on iOS in Intents, allowing a remote attacker to escape the iframe sandbox via a crafted HTML page.

The issue is related to insufficient policy enforcement in site isolation, allowing a remote attacker to bypass site isolation via a crafted HTML page. This can lead to unauthorized access to protected information. The vulnerability is associated with errors in authorization when using Blob URL in Google Chrome.

The issue allows sound fetched through audio elements to be exfiltrated cross-origin. This was addressed with improved audio taint tracking.

The issue is related to a lack of protection for service data in the Blink rendering module of Google Chrome. It allows a remote attacker to bypass the no-referrer policy and disclose protected information using a specially crafted HTML page.

The issue involves the `WebKit` component and allows remote attackers to execute arbitrary code or cause a denial of service, resulting in memory corruption and application crash, via a crafted web site.

A security feature bypass issue exists due to Microsoft Edge not properly enforcing same-origin policies. This could allow an attacker to access information from origins outside the current one. To exploit this issue, an attacker would need to trick a user into loading a page or visiting a website.

A security issue exists where Microsoft Edge fails to properly validate certain specially crafted documents, allowing an attacker to trick a user into loading a page with malicious content. This is due to the Edge Content Security Policy (CSP) failing to correctly apply the Same Origin Policy for HTML elements present in other browser windows.

A security feature bypass issue exists, allowing for the bypassing of Mixed Content warnings. This could enable the loading of unsecure content (HTTP) from secure locations (HTTPS).

The issue is related to a lack of protection for sensitive data in Microsoft Edge, which can be exploited by a remote attacker using a specially crafted website to obtain confidential information from the process memory.

The issue is related to the `htmlParseComment` function in `HTMLparser.c` of the libxml2 library, caused by a buffer overflow. This can be exploited by a remote attacker using an unclosed HTML comment to obtain sensitive information, cause a denial of service (application crash due to out-of-bounds heap memory access), or have other unspecified impacts.