Thai Duong

A use-after-free issue exists in the handling of PQC hybrid key-shares. A malicious TLS 1.3 server can send a truncated PQC hybrid KeyShare, which triggers an error cleanup path that operates on memory that has already been freed. PQC refers to Post-Quantum Cryptography, which are cryptographic algorithms designed to be secure against attacks by quantum computers.

CMS AuthEnvelopedData fails to enforce tag-length during the decryption process.

A heap use-after-free read occurs in the libblkid library during nested partition probing. The BSD, Minix, Solaris x86, and UnixWare partition probers cache a raw pointer to a parent partition entry within a dynamically allocated array. If subsequent partition additions trigger a reallocation of this array, the cached pointer becomes stale. An attacker can trigger this issue without user interaction by providing a crafted block device image, such as through a USB drive or a loop-mounted disk image, because libblkid is automatically executed as root by udev/udisks during block-device hot-plug events. This may result in denial of service or limited information disclosure.

A use-after-free condition occurs during PKCS#7 signature verification when processing a specially crafted PKCS#7 or S/MIME signed message. If the `SignedData` `digestAlgorithms` field is present as an empty ASN.1 SET, the `PKCS7 verify()` function may incorrectly free a BIO (Basic Input/Output abstraction) owned by the caller. A subsequent attempt by the application to use or free this BIO via `BIO free()` leads to memory corruption, process crashes, or potentially remote code execution. This issue affects applications using OpenSSL PKCS#7 APIs, while those using CMS APIs are not affected. FIPS modules in versions 4.0, 3.6, 3.5, 3.4, and 3.0 are not impacted as the affected code resides outside the FIPS module boundary.

A weak robustness vulnerability exists in the AWS Encryption SDKs due to the non-committing property of AES-GCM and other AEAD ciphers. This allows an attacker to craft a unique ciphertext that decrypts to multiple different results, particularly in a multi-recipient setting. The vulnerability also enables information leakage and ciphertext forgery attacks. An attacker can create ciphertexts that leak the user's AWS account ID, encryption context, user agent, and IP address upon decryption. Additionally, an attacker can create ciphertexts that are accepted by other users. The non-committing property of AES-GCM can cause nonidentical plaintexts when decrypting a single ciphertext with two different keys.

The issue is related to the use of insufficiently random values in the React Native Bluetooth Scan component of the Bluezone application. This could allow a remote attacker to interfere with COVID-19 contact tracing by using many IDs. The vendor disputes the relevance of this report, stating that the recipient of an alert will know it was a false alert if contact-history comparison fails.

The issue concerns the QuickType feature in the Keyboards subsystem, which collects typing-prediction data from fields even when the autocomplete attribute is set to off. This behavior potentially allows attackers to discover credentials by reading credential values within unintended DOM input elements.

The issue allows remote attackers to decrypt and modify encrypted View State form data via a padding oracle attack. This could possibly lead to forging cookies or reading application files. An information disclosure vulnerability exists due to improper error handling during encryption padding verification, allowing an attacker to read encrypted data, such as the view state. This vulnerability can also be used for data tampering, which could be used to decrypt and tamper with the data encrypted by the server. In Microsoft .NET Framework 3.5 Service Pack 1 and above, an attacker can retrieve the contents of any file within the ASP.NET application, including web.config.

The SSL protocol 3.0 uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, also known as the "POODLE" issue. This allows an attacker to decrypt some encrypted contents under certain conditions. The conditions of successful exploitation are somewhat similar to the BEAST attack, which requires several conditions to be met for successful exploitation, including a man-in-the-middle position in the network and the ability to direct the victim client to send many repeated requests to the vulnerable server on behalf of the attacker. Due to the conditions required of a successful attack scenario, the risk of exploitation is not particularly high.

The issue allows man-in-the-middle attackers to obtain plaintext HTTP headers by observing length differences during a series of guesses in which a string in an HTTP request potentially matches an unknown string in an HTTP header, also known as a "CRIME" attack.