libssl3t64: Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticateaserver may fail to notice that the server...

Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticateaserver may fail to notice that the server was not authenticated, becausehandshakes don't abort as expected when the SSL_VERIFY_PEER verificationmodeis set.Impact summary: TLS and DTLS connections using raw public keys may bevulnerable to man-in-middle attacks when server authentication failure isnotdetected by clients.RPKs are disabled by default in both TLS clients and TLS servers. Theissueonly arises when TLS clients explicitly enable RPK use by the server, andtheserver, likewise, enables sending of an RPK instead of an X.509 certificatechain. The affected clients are those that then rely on the handshake tofail when the server's RPK fails to match one of the expected public keys,by setting the verification mode to SSL_VERIFY_PEER.Clients that enable server-side raw public keys can still find out that rawpublic key verification failed by calling SSL_get_verify_result(), andthosethat do, and take appropriate action, are not affected. This issue wasintroduced in the initial implementation of RPK support in OpenSSL 3.2.The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by thisissue.

Where it's fixed