The issue arises from the `DoTls13CertificateVerify` function in `tls13.c`, which does not properly handle anomalous peer behavior. Specifically, it continues processing when it receives an ED22519, ED448, ECC, or RSA signature without the corresponding certificate. This affects the client side, allowing man-in-the-middle attackers to impersonate TLS 1.3 servers.