The vulnerability arises from libmongoc's SCRAM authentication implementation flaw where the client does not properly abort the handshake upon detecting a nonce mismatch in the server's first message. An attacker positioned as a man-in-the-middle can exploit this by injecting a malicious server-first-message containing a controlled salt and low iteration count. This manipulation leads the client to send the client proof, which the attacker can capture and use for offline password cracking attempts. The vulnerability is mitigated by TLS encryption, which prevents man-in-the-middle interception in typical production deployments.

An attacker with man-in-the-middle capabilities could exploit this vulnerability to capture authentication data (client proof) that enables offline password cracking. This could lead to compromise of user credentials if TLS is not used. However, since TLS is standard in production, the practical risk is reduced. There are no known exploits in the wild.

No official patch information is provided. The vulnerability is mitigated by using TLS, which is standard in production deployments of MongoDB. It is recommended to ensure all connections use TLS to prevent man-in-the-middle attacks. Check MongoDB's official advisories for any future patches or updates addressing this issue.