What hacking attack is challenge/response authentication used to prevent?

Challenge/response authentication works by sending a unique, time-sensitive 'challenge' to the client, which must compute a valid response using a shared secret. Since the challenge changes with each authentication attempt, an attacker cannot simply reuse (replay) a previously captured, valid response to gain unauthorized access.

Challenge/response authentication mechanisms do not directly prevent scanning attacks, which involve probing systems for open ports or vulnerabilities.

While it enhances overall security, challenge/response authentication primarily prevents replay attacks during the initial authentication phase, not directly session hijacking after authentication.

Challenge/response authentication makes password cracking more difficult by not transmitting the password directly, but its primary purpose is to prevent the replay of *authentication tokens*, not direct password guessing.