This vulnerability occurs when a system establishes a cryptographic key with another party without first confirming that party's true identity.
While a key exchange can encrypt the communication channel between two systems, it does not automatically verify who is on the other end. If you skip the authentication step, you might be securely talking to an imposter. This is like having a perfectly sealed, private conversation with someone who is pretending to be your bank—the privacy is intact, but you've trusted the wrong entity. In a typical attack, a client application mistakenly connects to a malicious server masquerading as a trusted one. If the client proceeds without checking the server's credentials, the fake server can steal user login details, intercept sensitive data, or relay information to the real server while monitoring the entire session. The attacker essentially sits in the middle, with both parties unaware their secure channel has been compromised from the start.
Impact: Bypass Protection Mechanism
No authentication takes place in this process, bypassing an assumed protection of encryption.
Impact: Read Application Data
The encrypted communication between a user and a trusted host may be subject to sniffing by any actor in the communication path.
High