Port 5900VNC Remote Desktop
Virtual Network Computing (VNC) allows users to remotely control another computer’s desktop across networks or the internet. Operating primarily on port 5900, VNC is widely compatible, supporting various implementations including Apple Remote Desktop. It facilitates graphical desktop sharing, enabling seamless access and management regardless of physical location..
- transport
- tcp · udp
- in transit
- cleartext
- assignment
- official
- risk
- 4/10
- lookups
- 14,234
2 transports registered
payload readable on path
registered with iana
caution
rank 247 of 993 · top 25%
Technical Details
what runs on :5900Overview
Virtual Network Computing (VNC) is a cross-platform protocol that facilitates remote graphical desktop sharing by transmitting keyboard and mouse events between client and server, paired with a framebuffer update mechanism. The default port it uses is 5900, with additional ports (5901, 5902, etc.) for concurrent sessions.
Protocols and Implementations
VNC is platform-agnostic and typically relies on the Remote FrameBuffer (RFB) protocol, which is simple yet versatile. Multiple open-source and commercial implementations exist, notably RealVNC, TightVNC, UltraVNC, and Apple Remote Desktop. It supports desktop sharing over both TCP and UDP and can be tunneled through encrypted connections such as SSH or VPN.
Use Cases and Connectivity
VNC is popular in IT administration, end-user support, education, and remote work scenarios. While primarily used over TCP for reliable session delivery, some implementations experiment with UDP for performance improvements. SCTP support is uncommon.
Security Information
exposure of :5900risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
remote access averages 4.0 across 110 ports — this one sits level with it.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
official
registered with iana for this service — scanners fingerprint it by number
reachable over
tcp · udp
udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite
security overview
Common Vulnerabilities
- Weak or no authentication: Many default VNC setups use minimal authentication (single password) or are configured insecurely.
- Plaintext transmission: Data transmitted is unencrypted, exposing sessions to eavesdropping and credential theft.
- Brute force attacks: Exposed VNC servers are frequent targets for automated password guessing.
- Exploitable implementations: Some VNC software versions contain buffer overflows or code execution vulnerabilities.
Common Mitigations
- Enable strong authentication: Use complex passwords and consider multi-factor authentication if available.
- Encrypt traffic: Tunnel VNC sessions over SSH or VPNs or use VNC variants with built-in encryption.
- Restrict access: Limit exposure via firewalls; allow connections only from trusted IP ranges.
- Keep software updated: Regularly patch and update VNC servers and clients.
- Monitor and log: Track login attempts and access patterns for suspicious behavior.
Related Ports
the 8 most looked-up other ports in remote access — 110 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :8000 | Intel Remote Desktop / Alternate HTTP Port | TCP | Web Services | safe | 84.3k |
| :8888 | D2GS Admin Console | TCP | Remote Access | caution | 83.7k |
| :8881 | Atlasz Secure Server | TCP | Web Services | caution | 67.6k |
| :5938 | TeamViewer | TCPUDP | Remote Access | caution | 65.0k |
| :8291 | Winbox MikroTik Admin | TCP | Security | caution | 62.9k |
| :8008 | IBM HTTP Server Admin | TCP | Web Services | caution | 58.3k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :23 | Telnet | TCP | Remote Access | caution | 34.8k |
risk mix of the 8 listed
- safe13%
- caution88%
0 of 8 encrypted