CEH Practice Question: Advanced Topics: Wireless, Cloud, IoT, Cryptography

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  A vulnerability in the TLS 1.3 handshake

  Why it's wrong here

  A vulnerability in the TLS 1.3 handshake is incorrect because TLS 1.3 was specifically designed with robust mechanisms to prevent downgrade attacks. It removed support for insecure legacy features and incorporated explicit downgrade protection into its handshake protocol. Therefore, the vulnerability exploited in a downgrade attack does not reside within TLS 1.3 itself, but rather in the negotiation process that allows a client or server to fall back to older, less secure protocols.

• ✗

  A known weakness in the Diffie-Hellman key exchange

  Why it's wrong here

  A known weakness in the Diffie-Hellman key exchange is incorrect because while Diffie-Hellman (DH) can have its own vulnerabilities (e.g., weak prime numbers or insufficient group sizes as seen in Logjam), these are distinct from a downgrade attack. A downgrade attack specifically targets the protocol version negotiation, forcing the use of an entirely weaker protocol suite (like SSLv3 or TLS 1.0) rather than exploiting a flaw within a specific cryptographic primitive like DH itself, which might be used across various TLS versions.

• ✓

  The fallback mechanism in SSL/TLS implementations

  Why this is correct

  The fallback mechanism in SSL/TLS implementations is the correct answer because many older SSL/TLS client implementations included a compatibility fallback mechanism. If the initial handshake with a preferred, stronger protocol version failed, the client would attempt to re-establish the connection using an older, less secure protocol version. An attacker exploits this by intercepting the initial ClientHello, blocking the server's preferred protocol response, and then tricking the client into initiating a connection with a vulnerable, older protocol like SSLv3, thereby enabling further exploitation.

• ✗

  The ability to modify the ClientHello message

  Why it's wrong here

  The ability to modify the ClientHello message is incorrect because while an attacker must indeed modify or manipulate the ClientHello message as part of a man-in-the-middle (MITM) attack to initiate a downgrade, this ability is a *means* to an end, not the root vulnerability. The core issue that enables the downgrade attack is the client's or server's willingness to fall back to an older, less secure protocol version when a preferred, stronger one fails. The attacker exploits this inherent fallback behavior by manipulating the communication flow, often via ClientHello modification.