The issue occurs when a DTLS resumption handshake falls back to a DTLS full handshake on a parameter mismatch without using a HelloVerifyRequest. This can result in message amplification, potentially leading to DDoS attacks on other peers, and high CPU load, leading to a DoS attack on the own peer. The misbehavior is specific to configurations where DTLS VERIFY PEERS ON RESUMPTION THRESHOLD values are larger than 0, especially when used with certificate-based cipher suites.