CVE-2026-7830: UltraVNC MS-Logon II uses 64-bit Diffie-Hellman and seeded libc rand() enabling credential interception
UltraVNC through 1.8.2.2 uses inadequate cryptography in the MS-Logon II authentication scheme (rfbUltraVNCMsLogonIIAuth). In rfb/dh.cpp the Diffie-Hellman key exchange is performed with parameters that fit in an unsigned 64-bit integer (DHMAXBITS 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-7830?
The severity of CVE-2026-7830 is high with a score of 7.4.
What are the risks associated with CVE-2026-7830?
CVE-2026-7830 poses risks of credential interception due to inadequate cryptography in the authentication scheme.
How does CVE-2026-7830 affect UltraVNC users?
CVE-2026-7830 affects UltraVNC users by potentially allowing attackers to intercept credentials through weak encryption.
What versions of UltraVNC are vulnerable to CVE-2026-7830?
UltraVNC versions up to and including 1.8.2.2 are vulnerable to CVE-2026-7830.
How can I mitigate the risks of CVE-2026-7830?
To mitigate the risks of CVE-2026-7830, users should update to a patched version of UltraVNC that addresses the cryptography weakness.