Description
UltraVNC through 1.8.2.2 uses a cryptographically weak pseudo-random number generator to produce VNC authentication challenge bytes. In rfb/vncauth.c:119-129, the vncRandomBytes() function seeds libc rand() with time(0) + getpid() + rand() and generates a 16-byte challenge. The combined seed space is approximately 31 bits (libc rand() internal state) and is entirely determined by publicly-observable values (wall-clock time and process ID). An attacker who can observe the authentication exchange can enumerate the seed space and predict the challenge within seconds, enabling forgery or offline brute-forcing of responses. Note: on Windows, the active code path may use vncEncryptBytes2.cpp which calls CryptGenRandom; reachability on shipped Windows binaries requires compile-graph verification and is under investigation.
Problem types
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/...-rand-weak-rng-vnc-auth-challenge-ultravnc