Axel Chong

يوجد ثغرة أمنية تسمح للروابط الموجودة داخل إطار iframe في بيئة الحماية (sandbox) بتشغيل تطبيق خارجي على أجهزة Android، متجاوزةً بذلك أذونات ”allow-“ المطلوبة. وقد يؤدي ذلك إلى السماح بالوصول غير المصرح به أو تشغيل التطبيقات.

ترتبط الثغرة الأمنية في Mozilla Firefox على أنظمة التشغيل Android بخلل في آلية حماية البيانات. قد يتيح استغلال هذا الخلل عن بُعد للمهاجم التحايل على قيود الأمان الحالية.

The issue is related to an inappropriate implementation in the WebApp Provider component of Google Chrome, which may allow a remote attacker to obfuscate the security UI via a crafted HTML page. This could potentially lead to unauthorized access to protected information. The severity of this issue is considered low.

The issue is related to the Picture in Picture technology in Google Chrome, where a remote attacker can exploit it to spoof the contents of the URL bar using a specially crafted HTML page. This can lead to the distortion of important information in the user interface.

The issue is related to an inappropriate implementation in DevTools, allowing an attacker to bypass discretionary access control via a crafted Chrome Extension if a user is convinced to install a malicious extension. Additionally, there is a buffer overflow vulnerability that can be exploited by a remote attacker using a specially crafted PDF file, potentially allowing the execution of arbitrary code.

The issue is related to an inappropriate implementation in the Extensions API, allowing an attacker to bypass an enterprise policy via a crafted HTML page. This could enable a remote attacker to gain unauthorized access to protected information using a specially crafted HTML page.

The issue is related to an inappropriate implementation in the Picture in Picture feature of Google Chrome, allowing a remote attacker to spoof security UI via a crafted HTML page. This could enable the attacker to bypass security restrictions. The severity of this issue is classified as Low by Chromium.

The issue is related to an inappropriate implementation in Interstitials, allowing a remote attacker to obfuscate security UI via a crafted HTML page. This could enable the attacker to bypass security restrictions. The severity of this issue is classified as Low by Chromium.

The issue is related to an inappropriate implementation in the Input component of Google Chrome, which can be exploited by a remote attacker to spoof the security UI via a crafted HTML page. This can potentially allow an attacker to manipulate the user interface.

The issue is related to insufficient policy enforcement in the Extensions API of Google Chrome, allowing a remote attacker to bypass existing security restrictions. This can be achieved by convincing a user to install a malicious extension, which can then use a crafted HTML page to bypass an enterprise policy.

The issue is related to an inappropriate implementation in Color, allowing a remote attacker to obfuscate security UI via a crafted HTML page. This could enable the attacker to bypass existing security restrictions. The severity of this issue is classified as Medium by Chromium.

The issue is related to insufficient policy enforcement in the Extensions API of Google Chrome, allowing a remote attacker to install arbitrary extensions using a specially crafted HTML page. This could enable an attacker to bypass an enterprise policy if a user is convinced to install a malicious extension.

The issue is related to the use of `module.constructor.createRequire()`, which can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This affects all users using the experimental policy mechanism in the mentioned release lines. The policy is an experimental feature of Node.js.

A bug in popup notifications delay calculation could have made it possible for an attacker to trick a user into granting permissions. This issue is related to incorrect handling of insufficient permissions due to an error in the calculation of the delay of popup notifications, which may allow a remote attacker to conduct clickjacking attacks.

A vulnerability has been discovered in the experimental permission model of Node.js, specifically related to improper handling of Buffers in file system APIs, causing a traversal path to bypass when verifying file permissions. This issue affects all users using the experimental permission model in Node.js 20. The vulnerability can be exploited by specifying a path traversal sequence in a Buffer, allowing an attacker to bypass security restrictions and gain unauthorized access to protected information.

The issue arises from a missing check in the `fs.mkdtemp()` API, allowing a malicious actor to bypass the permission model check using a path traversal attack. This can lead to the creation of an arbitrary directory. The vulnerability affects all users using the experimental permission model in Node.js.

The issue is related to an inappropriate implementation in the Web Browser UI, allowing a remote attacker to potentially spoof the contents of an iframe dialog context menu via a crafted HTML page. This could be exploited by a remote attacker using a specially crafted HTML page.

A vulnerability has been discovered in Node.js, specifically within the experimental permission model. This flaw relates to improper handling of path traversal bypass when verifying file permissions. The vulnerability may allow a remote attacker to impact the integrity of protected information due to incorrect restriction of the directory path name with limited access.

The issue is related to the use of ` proto ` in `process.mainModule. proto .require()`, which can bypass the policy mechanism and allow requiring modules outside of the `policy.json` definition. This affects users of the experimental policy mechanism in the mentioned release lines. The policy is noted as an experimental feature of Node.js at the time of issue identification.

The issue is related to insufficient protection of internal data when handling the "Save Link As" dialog, allowing an attacker to gain unauthorized access to protected information. This occurs when suggested filenames contain environment variable names, which are resolved in the context of the current user. The vulnerability affects Firefox and Thunderbird on Windows, allowing a remote attacker to access confidential information in the system.