Common attacks and weaknesses
- Same directory exposure as LDAP if reachable from untrusted networks.
- Expired or self-signed certificates disabling validation in clients.
LDAP over TLS.
The client proves who it is on port 636 and gets an answer (or a ticket) it can use with other services. Everything is encrypted: someone on the path only sees unreadable bytes.
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| ldaps | 636 | TCP, UDP | ldap protocol over TLS/SSL (was sldap) | - | - |
// source: IANA service name and port number registry
Linux
sudo ss -ltnup 'sport = :636' # process listening on 636
sudo lsof -nP -i :636macOS
sudo lsof -nP -i :636
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 636 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 636 netstat -ano | findstr :636
From another machine
nmap -p 636 -sV <host> sudo nmap -sU -p 636 <host> nc -zv <host> 636
Block it in the firewall
sudo ufw deny 636/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 636" -Direction Inbound -LocalPort 636 -Protocol TCP -Action Block # Windows
LDAP over TLS.
Port 636 is registered for TCP and UDP. In practice the service mostly uses TCP.
It is rated 5/10 (moderate) when exposed to the Internet. Same directory exposure as LDAP if reachable from untrusted networks. Restrict to internal networks.
On Linux run "ss -ltnup 'sport = :636'", on macOS "lsof -nP -i :636", and on Windows "netstat -ano | findstr :636" to see the local process. From another machine, "nmap -p 636 <host>" shows whether it is reachable.