Description
UltraVNC through 1.8.2.2 uses inadequate cryptography in the MS-Logon II authentication scheme (rfbUltraVNC_MsLogonIIAuth). In rfb/dh.cpp the Diffie-Hellman key exchange is performed with parameters that fit in an unsigned 64-bit integer (DH_MAX_BITS controls the prime size). A 64-bit DH key can be broken by Pollard's rho algorithm in under one second on current hardware. Additionally, the private exponent is generated by the rng() function, which multiplies three libc rand() values seeded from time(NULL). With approximately 31 bits of internal state and a time-based seed, the private exponent is recoverable in under a minute by a passive observer. A network attacker who can observe the MS-Logon II handshake (via sniffing, recording, or man-in-the-middle) can derive the shared DH key and decrypt the encapsulated username and password, resulting in full credential disclosure. This affects legacy MS-Logon II connections; MS-Logon III (X25519 + AES-256-GCM) is unaffected.
Problem types
Inadequate Encryption Strength
Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Product status
Any version
Timeline
| 2026-06-02: | Vulnerability discovered during security audit |
| 2026-06-17: | Reported to vendor (coordinated disclosure) |
| 2026-09-15: | Planned public disclosure (90-day window) |
Credits
Arjun Basnet, Securin (arjun.basnet@securin.io)
References
uvnc.com/ (UltraVNC project page)
github.com/ultravnc/UltraVNC (UltraVNC source repository)
www.securin.io/...-ms-logon-credential-interception-ultravnc