Marcus Brinkmann

اسم البرنامج المعرض للخطر والإصدارات المتأثرة: إصدارات خادم Apache HTTP حتى الإصدار 2.4.63 الوصف: في بعض إعدادات mod ssl، يمكن لمهاجم من نوع «man-in-the-middle» اختطاف جلسة HTTP من خلال هجوم ترقية TLS. تؤثر هذه المشكلة على الإعدادات التي تستخدم «SSLEngine optional» لتمكين ترقيات TLS. يرتبط هذا الهجوم بعدم تزامن HTTP. التوصيات: قم بالتحديث إلى الإصدار 2.4.64، الذي يلغي دعم ترقية TLS.

تنشأ المشكلة من بعض رسائل البريد الإلكتروني MIME التي تم التلاعب بها، والتي تزعم أنها تحتوي على رسالة مشفرة بواسطة OpenPGP، ولكنها في الواقع تحتوي على رسالة موقعة بواسطة OpenPGP، والتي يتم عرضها بشكل خاطئ على أنها مشفرة.

The issue is related to the implementation of the S/MIME standard in the Thunderbird email client, specifically with errors in checking the cryptographic signature due to a mismatch in the date and time of its creation. This could allow a remote attacker to impact the confidentiality, integrity, and availability of protected information by giving recipients the impression that a message was sent at a different date or time.

The issue is related to errors in handling OpenPGP cryptographic signatures. Exploitation of this issue may allow a remote attacker to perform a spoofing attack. When processing a PGP/MIME payload that contains digitally signed text, the first paragraph of the text was not shown to the user because it was interpreted as a MIME message and treated as an email header section. This could be used to spoof an email message, potentially using a digitally signed text from a different context.

The issue is related to OS command injection in OpenSSH, which might occur if a user name or host name has shell metacharacters and this name is referenced by an expansion token in certain situations. For example, an untrusted Git repository can have a submodule with shell metacharacters in a user name or host name. The estimated number of potentially affected devices worldwide is around 116,742,290, mainly distributed in the United States, China, and other countries.

The issue is related to errors in key management in the ssh-agent tool of OpenSSH. It allows an attacker to disclose protected information by exploiting certain destination constraints that are not fully applied when adding PKCS#11-hosted private keys. Specifically, when destination constraints are specified, they are only applied to the first key, even if a PKCS#11 token returns multiple keys. This can be exploited by sending a specially crafted request to obtain sensitive information, which can then be used to launch further attacks against the affected system.

The SSH transport protocol with certain OpenSSH extensions is vulnerable to a prefix truncation attack, known as the Terrapin attack. This attack allows a man-in-the-middle attacker to strip an arbitrary number of messages right after the initial key exchange, breaking SSH extension negotiation and downgrading connection security. The attack works by injecting arbitrary SSH MSG IGNORE messages during the initial key exchange and removing the same number of messages just after the initial key exchange has concluded. This is possible due to missing authentication of the excess SSH MSG IGNORE messages and the fact that the implicit sequence numbers used within the SSH protocol are only checked after the initial key exchange.

The issue is related to insufficient authentication data verification in the implementation of the SSH protocol in PuTTY. This can allow a remote attacker to gain unauthorized access to protected information. Specifically, PuTTY proceeds with establishing an SSH session even if it has never sent a substantive authentication response, making it easier for an attacker-controlled SSH server to present a later spoofed authentication prompt. This can be used to capture credential data for purposes undesired by the client user.

The issue is related to errors in privilege management within the Windows HTML Platform component of the Windows operating system. This can allow a remote attacker to bypass existing security restrictions.

The issue is related to the Secure/Multipurpose Internet Mail Extensions (S/MIME) functionality in the Thunderbird email client, specifically concerning the lack of protection for certain data. This could allow a remote attacker to gain unauthorized access to protected information. Additionally, it is noted that encrypted S/MIME parts in a crafted multipart/alternative message can leak plaintext when included in an HTML reply or forward.

The issue lies in the signature verification routine of the install.sh script, which only checks if a yarn release is signed by any key in the user's local keyring. This does not ensure the release is signed by the official yarn release key, allowing remote attackers to sign tampered packages with their own key.

The issue concerns the signature verification routine, which fails to verify the status of the signature and the validity of the signing key. This allows remote attackers to spoof arbitrary email signatures by crafting a signed email with an invalid signature or by creating a key with a fake user ID (email address) and injecting it into the user's keyring.

An issue in the password-store.sh script of Simple Password Store allows remote attackers to spoof file signatures on configuration files and extension scripts due to an incomplete regular expression in the signature verification routine. This can lead to the disclosure of passwords if an attacker modifies the configuration file to inject additional encryption keys. Furthermore, modifying the extension scripts can allow the attacker to execute arbitrary code.

The issue concerns the signature verification routine, which incorrectly interprets user ids as status/control messages and fails to track the status of multiple signatures. This allows remote attackers to spoof arbitrary email signatures via public keys containing crafted primary user ids.

The issue is related to the mishandling of the original filename during decryption and verification actions in the mainproc.c component. This allows remote attackers to spoof output sent to other programs using the "--status-fd 2" option, potentially affecting the integrity of protected information. For instance, an OpenPGP data representation of an original filename with line feed characters, in conjunction with GOODSIG or VALIDSIG status codes, can be exploited.