Simo Sorce

Applications using RSASVE key encapsulation can send contents of an uninitialized memory buffer to a malicious peer, potentially leading to sensitive data leakage. This occurs when applications use `EVP PKEY encapsulate()` with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key. The `RSA public encrypt()` function returns the number of bytes written on success and -1 on error, but the affected code only checks if the return value is non-zero. If RSA encryption fails, the encapsulation can still return success, allowing the caller to use uninitialized ciphertext. Calling `EVP PKEY public check()` or `EVP PKEY public check quick()` before `EVP PKEY encapsulate()` can mitigate this issue.

A security issue has been identified in the pkcs11-provider, associated with Public-Key Cryptography Standards (PKCS#11). If exploited, this could result in a Bleichenbacher-like security flaw, potentially enabling a side-channel attack on PKCS#11 1.5 decryption.

The issue allows remote attackers to request an arbitrary SAN name for services.

The issue is related to multiple memory leaks in the kadmin/server/server stubs.c file in kadmind, which can be exploited by remote authenticated users to cause a denial of service through memory consumption. This can be achieved by sending a request with a NULL principal name.

The issue allows attackers to bypass intended access restrictions and modify directory entries. This is achieved through a crafted ldapmodrdn call.

The issue affects the Key Distribution Center (KDC) in MIT Kerberos 5, allowing remote authenticated users to cause a denial of service via a crafted TGS request. This can lead to a NULL pointer dereference and daemon crash. The vulnerability may compromise the confidentiality, integrity, and availability of protected information.