VNC Brute Force and Default Credential Exploitation
VNC uses a single shared password with no username. The password is capped at 8 characters — anything beyond that is silently truncated by most implementations. Many deployments ship with blank passwords, weak defaults, or authentication disabled entirely. A successful login gives a full graphical desktop session.
Before running a wordlist attack, check if the target accepts connections with no password at all. That is faster and common in labs.
Checking for No Authentication
The Nmap NSE script vnc-info shows which security types the server offers:
If the output includes Security types: None or Type 1 - None, connect directly:
Press Enter at any password prompt without typing anything. On misconfigured servers this completes immediately. For a dedicated no-auth page see https://hackindex.io/services/vnc/exploitation/unauthenticated-access.
Brute Force with Hydra
-t 4 limits threads — VNC servers disconnect or lock out under high concurrency. Keep threads low. For a non-standard port:
[5900][vnc] host: 10.10.10.10 password: password1
Brute Force with Medusa
Brute Force with crowbar
crowbar handles the RFB protocol reliably and is worth trying when Hydra gives inconsistent results:
-n 1 forces a single thread — essential for VNC stability.
Filtering the Wordlist for 8-Character Limit
VNC passwords are truncated at 8 characters. Filter rockyou.txt to speed up the attack significantly:
Common Default VNC Passwords
Try these first before running a full wordlist:
(blank — press Enter)
password
1234
admin
vnc
secret
12345678
Connecting After a Successful Find
Supply the password at the prompt. For non-standard ports:
Non-Standard Port Mapping
VNC display numbers map to ports as 5900 + display. Display 0 is 5900, display 1 is 5901, and so on. Any open port in the 5900–5910 range is likely VNC.
References
-
galkan VNC brute force module documentation.
-
VNC module documentation and thread tuning guidance.
Was this helpful?
Your feedback helps improve this page.