Tavis Ormandy

يوجد ثغرة أمنية من نوع «التنفيذ البرمجي عبر المواقع» (XSS) المخزنة في Adobe Experience Manager. يمكن لمهاجم يتمتع بامتيازات محدودة استغلال هذه الثغرة لإدخال نصوص برمجية ضارة في حقول النماذج المعرضة للخطر. قد يتم تنفيذ جافا سكريبت ضار في متصفح الضحية عند تصفح صفحة تحتوي على الحقل المعرض للخطر.

البرنامج معرض لثغرة أمنية من نوع «التنفيذ البرمجي عبر المواقع» (XSS) المخزّن. يمكن للمهاجم الذي يتمتع بامتيازات منخفضة استغلال هذه الثغرة لإدخال نصوص برمجية ضارة في حقول النماذج المعرضة للخطر. وقد يتم تنفيذ جافا سكريبت ضار في متصفح الضحية عند الوصول إلى الصفحة التي تحتوي على الحقل المعرض للخطر.

تتعلق المشكلة بالتحقق غير السليم من التوقيع في أداة تحميل تصحيحات الميكروكود الخاصة بذاكرة القراءة فقط (ROM) لمعالجات AMD، مما قد يسمح لمهاجم يتمتع بامتيازات المسؤول المحلي بتحميل ميكروكود ضار للمعالج. وقد يؤدي ذلك إلى فقدان سرية وسلامة نظام ضيف سري يعمل في إطار تقنية AMD SEV-SNP. تستغل هذه الثغرة الأمنية استخدام دالة تجزئة غير آمنة لتحديثات الرموز الدقيقة، مما قد يعرض بيئات الحوسبة الآمنة للخطر.

A sequence of processor instructions can lead to unexpected behavior in some Intel processors, potentially allowing an authenticated user to enable escalation of privilege, information disclosure, or denial of service via local access. This issue is related to the interpretation of redundant prefixes and can cause the system to crash or become unresponsive. The vulnerability, termed Reptar, primarily affects multi-tenant virtualized environments where multiple virtual machines are run on the same host.

The issue in AMD Zen 2 processors, under specific microarchitectural circumstances, may allow an attacker to potentially access sensitive information. This is due to a use-after-free vulnerability, which can be exploited to track the contents of registers during the execution of other processes on the same CPU core. Researchers have found that 62% of AWS environments are potentially vulnerable to this issue, and it may affect various AMD Ryzen processors. The vulnerability can be used to steal confidential data, such as passwords and encryption keys.

A critical issue has been found in uTorrent, affecting some unknown processing of the component Guest Account. The manipulation leads to privilege escalation. The attack may be initiated remotely.

A critical issue has been found, affecting an unknown functionality of the HTTP RPC Server component, which can lead to privilege escalation. This issue can be exploited remotely.

A critical issue has been found in uTorrent, affecting an unknown part of the software. The manipulation of this issue leads to memory corruption and can be initiated remotely.

A critical issue was found in uTorrent, affecting the PRNG component, which leads to weak authentication. The attack can be initiated remotely.

The issue is related to a buffer overflow in the `mutt decode uuencoded()` function of the Mutt email client. This can allow a remote attacker to gain unauthorized access to protected information or cause a denial of service. The problem arises from the function reading past the end of an input line.

The BN mod sqrt() function in OpenSSL contains a bug that can cause it to loop forever for non-prime moduli, leading to a denial of service attack. This issue can be triggered by crafting a certificate with invalid explicit curve parameters. The vulnerability affects various situations, including TLS clients and servers consuming certificates, hosting providers, and certificate authorities parsing certification requests. The issue was addressed in the releases of OpenSSL 1.1.1n and 3.0.2 on March 15, 2022.

The issue is related to a buffer overflow in the `set sixel` function within the `graphics sixel.c` component of the xterm terminal emulator. This occurs when Sixel support is enabled and an attacker provides crafted text. The vulnerability can be exploited by a remote attacker to cause a denial of service.

The issue is related to the incorrect handling of an empty pkcs7 sequence in certificate data. This could lead to a crash when handling an untrusted certificate, potentially allowing a remote attacker to cause a denial-of-service (DoS) condition by sending a specially crafted certificate. It is believed that this crash is not exploitable for more severe attacks.

The issue is related to a heap overflow when processing S/MIME messages, specifically those containing certificates with DER-encoded DSA or RSA-PSS signatures.

The issue exists due to insufficient input validation in Microsoft Defender, which is part of the Windows operating system. Exploitation of this issue may allow an attacker to cause a denial of service.

A null pointer dereference issue was addressed with improved input validation, which may allow a remote attacker to cause a denial of service.

The issue arises from the Debian xscreensaver package having the cap net raw capability enabled for the /usr/libexec/xscreensaver/sonar file. This setting can be exploited by local users to gain privileges, potentially due to incompatibility with the design of the Mesa 3D Graphics library dependency.

The issue is related to the `X509 issuer and serial hash()` function, which attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However, it fails to correctly handle any errors that may occur while parsing the issuer field, potentially resulting in a NULL pointer dereference and a crash, leading to a potential denial of service attack. This function is never directly called by OpenSSL itself, so applications are only vulnerable if they use this function directly and they use it on certificates that may have been obtained from untrusted sources. Additionally, calls to `EVP CipherUpdate`, `EVP EncryptUpdate`, and `EVP DecryptUpdate` may overflow the output length argument in some cases, causing applications to behave incorrectly or crash.

Name of the Vulnerable Software and Affected Versions: xterm versions before Patch #366 Description: The issue allows remote attackers to execute arbitrary code or cause a denial of service (segmentation fault) via a crafted UTF-8 combining character sequence. This can potentially lead to unspecified other impacts. Recommendations: For xterm versions before Patch #366, apply Patch #366 to resolve the issue. As a temporary workaround, consider restricting the use of crafted UTF-8 combining character sequences until the patch is applied.

The issue is related to incorrect handling of UTF-8 character sequences in the encoding.c component of GNU Screen. This can be exploited by a remote attacker to gain access to confidential data, compromise data integrity, and cause a denial of service, potentially leading to an application crash.