Common Network Port Vulnerabilities and Risk Mitigation
⏳ 2 min readAn auditing reference matrix for service ports frequently targeted by malicious network traffic.
The Anatomy of Network Ports
A network port is a logical construct that identifies a specific process or service on a machine. While IP addresses identify the machine itself, ports identify the application receiving the data. There are 65,535 available ports in TCP/UDP.
High-Risk Ports Reference Matrix
When validating firewall rules and performing threat modeling, ensure that the following ports are strictly denied from public internet ingress. They should only be accessible via trusted internal subnets or encrypted VPN tunnels:
| Port | Protocol | Common Service | Primary Risk / Attack Vector |
|---|
| `20/21` | TCP | FTP | Cleartext transmission of usernames, passwords, and data payloads. Highly susceptible to packet sniffing. |
|---|
| `22` | TCP | SSH | Automated botnet brute-force attacks and dictionary credentials guessing. |
|---|
| `23` | TCP | Telnet | Completely unencrypted remote administration. Trivial to eavesdrop and hijack sessions. |
|---|
| `3389` | TCP | RDP | Windows Remote Desktop is heavily targeted by ransomware syndicates for unauthorized entry. |
|---|
| `445` | TCP | SMB | Used for Windows file sharing. Exploits like EternalBlue (WannaCry) spread laterally via this port. |
|---|
| `1433` | TCP | MSSQL | Direct database exposure allows for SQL injection and brute-forcing of the 'sa' admin account. |
|---|
Hardening and Mitigation Recommendations
To secure these services, implement a 'Default-Deny' inbound posture. If remote administration is required, never expose RDP or SSH directly to the internet.
Instead, require administrators to authenticate to an IPsec or WireGuard VPN first. Once tunneled into the internal network, they can access the management ports securely.
Additionally, implement Rate Limiting (fail2ban) on internal SSH ports to thwart lateral brute-force attempts.