CyberHunter
Local dataset, no network
// Directory & authentication

Port 4952: SAG Directory Server

Port 4952 is assigned by IANA to sagxtsds (SAG Directory Server).

4952

How sagxtsds works

Directory & authentication
userdirectorysagxtsdsresponse userdirectorysagxtsdsresponse

The client proves who it is on port 4952 and gets an answer (or a ticket) it can use with other services.

Transport
TCP · UDP
Exposure risk
not rated depends on the program listening
Encryption
Unknownnot stated by the registry
IANA status
Assigned1 registered service
Range
Registered (1024-49151)
Category
Directory & authentication
01 Security

Is port 4952 dangerous?

We have no specific security note for port 4952. Its risk depends on the program actually listening on it. General advice for directory & authentication services:

  • Keep directory and authentication services on internal networks.
  • Require signing or TLS and disable anonymous queries.
  • Monitor authentication failures for spraying and brute force.
02 Registry

IANA registry entries for port 4952

ServicePortTransportDescriptionReferenceUpdated
sagxtsds 4952 TCP, UDP SAG Directory Server - 2006-01

// source: IANA service name and port number registry

03 Check it

Which program uses port 4952, and is it reachable?

Linux

sudo ss -ltnup 'sport = :4952'      # process listening on 4952
sudo lsof -nP -i :4952

macOS

sudo lsof -nP -i :4952

Windows (PowerShell)

Get-NetTCPConnection -LocalPort 4952 -State Listen | Select LocalAddress, OwningProcess
Get-NetUDPEndpoint -LocalPort 4952
netstat -ano | findstr :4952

From another machine

nmap -p 4952 -sV <host>
sudo nmap -sU -p 4952 <host>
nc -zv <host> 4952

Block it in the firewall

sudo ufw deny 4952/tcp                                         # Linux (ufw)
New-NetFirewallRule -DisplayName "Block 4952" -Direction Inbound -LocalPort 4952 -Protocol TCP -Action Block  # Windows
04 FAQ
What is port 4952 used for?

Port 4952 is assigned by IANA to sagxtsds (SAG Directory Server).

Is port 4952 TCP or UDP?

Port 4952 is registered for TCP and UDP.

Is it safe to open port 4952?

It depends on the program that listens on it. Open it only for a service you know and only to the networks that need it. Keep directory and authentication services on internal networks.

How do I check if port 4952 is open?

On Linux run "ss -ltnup 'sport = :4952'", on macOS "lsof -nP -i :4952", and on Windows "netstat -ano | findstr :4952" to see the local process. From another machine, "nmap -p 4952 <host>" shows whether it is reachable.

05 Related
:389 LDAP tcp · udp · high risk :636 LDAPS tcp · udp · moderate risk :88 Kerberos tcp · udp · high risk :3268 Global Catalog (LDAP) tcp · udp · high risk :1812 RADIUS udp · tcp · moderate risk :31 MSG Authentication tcp · udp :49 Login Host Protocol (TACACS) tcp · udp :56 XNS Authentication tcp · udp

Latest vulnerability news

All news