SY0-301 · Question #718
Which of the following wireless protocols could be vulnerable to a brute-force password attack? (Select TWO).
The correct answer is A. WPA2-PSK E. WPA - LEAP. WPA2-PSK and WPA-LEAP are both vulnerable to brute-force or dictionary attacks because they rely on shared secrets or weak challenge-response authentication that can be attacked offline.
Question
Which of the following wireless protocols could be vulnerable to a brute-force password attack? (Select TWO).
Options
- AWPA2-PSK
- BWPA - EAP - TLS
- CWPA2-CCMP
- DWPA -CCMP
- EWPA - LEAP
- FWEP
How the community answered
(24 responses)- A71% (17)
- B4% (1)
- C13% (3)
- D4% (1)
- F8% (2)
Why each option
WPA2-PSK and WPA-LEAP are both vulnerable to brute-force or dictionary attacks because they rely on shared secrets or weak challenge-response authentication that can be attacked offline.
WPA2-PSK (Pre-Shared Key) is vulnerable to offline brute-force and dictionary attacks because the 4-way handshake can be captured and the passphrase guessed repeatedly without interacting with the network.
WPA-EAP-TLS uses mutual certificate-based authentication - there is no shared password to brute-force, making offline password attacks infeasible.
WPA2-CCMP refers to the AES-based encryption cipher used in WPA2 and is not itself an authentication mechanism susceptible to brute-force password attacks.
WPA-CCMP similarly describes the encryption component of WPA and does not define an authentication method that is brute-forceable via password guessing.
WPA-LEAP (Cisco LEAP) uses MS-CHAPv2-based authentication which is known to be weak and vulnerable to offline dictionary and brute-force attacks, as exploited by tools like ASLEAP.
WEP is broken through IV (initialization vector) statistical attacks that recover the key by capturing enough packets, not through a direct brute-force password attack.
Concept tested: Wireless authentication protocols vulnerable to brute-force
Source: https://www.cisco.com/c/en/us/products/security/what-is-network-access-control.html
Topics
Community Discussion
No community discussion yet for this question.