Notes OSCP Concepts

Concepts

Network Services Handbook

Port numbers suggest what may be running, but the banner and protocol response decide what the service actually is. Use this page as a map, then follow the service note for commands and decisions.

Core Services

The ratings describe how services usually contribute to OSCP-style attack chains:

  • High: commonly worth immediate attention for that role.
  • Medium: regularly useful, but usually needs a supporting weakness.
  • Low: mainly provides information or access after another step.
  • Conditional: powerful when credentials, permissions, or a specific misconfiguration are present.

Privilege-escalation relevance includes exposing credentials or a misconfiguration that leads to higher privileges. It does not mean the remote port itself is a local privilege-escalation vulnerability.

Port(s)ProtocolWhat it doesInitial footholdPrivilege escalationFirst question
21FTPTransfers files over separate control and data connectionsMediumLowIs anonymous access allowed, and is anything readable or writable? See FTP Enumeration
22SSHProvides encrypted remote shell access and file transferConditionalLowAre credentials or a private key already available, and does it even accept passwords? See Brute Forcing Logins
25SMTPTransfers email between mail systemsMediumLowDoes the banner expose an old daemon, or can users be enumerated? See SMTP Enumeration
53 TCP/UDPDNSResolves names and stores domain recordsLowLowCan the server disclose records or transfer its zone? See DNS Enumeration
80/443HTTP/HTTPSServes web applications and APIsHighMediumWhat application, content, and virtual hosts are exposed? See Web Content Discovery
88 TCP/UDPKerberosIssues authentication tickets in an Active Directory domainMediumHighIs this a domain controller, and which domain and users exist?
111 TCP/UDPrpcbindMaps Unix RPC programs such as NFS to their listening portsLowConditionalWhich RPC programs are registered? See RPC Enumeration
135MSRPC Endpoint MapperMaps Windows RPC interfaces to dynamic high portsLowMediumWhich Windows services and management interfaces are exposed? See RPC Enumeration
139/445NetBIOS/SMBProvides Windows file, printer, named-pipe, and remote administration accessHighHighCan shares or host information be read anonymously or with known credentials? See SMB Enumeration
161 UDPSNMPExposes device and host management informationMediumMediumDoes a default or weak community string allow a walk? See SNMP Enumeration
389/636LDAP/LDAPSQueries directory objects such as users, groups, and computersLowHighIs anonymous bind allowed, or are domain credentials available?
1433MSSQLHosts Microsoft SQL Server databasesConditionalHighAre credentials available, and can the account execute OS commands? See Database Enumeration
2049NFSShares Unix filesystems over the networkMediumHighWhich exports are visible and mountable? See NFS no_root_squash
3306MySQLHosts MySQL or MariaDB databasesConditionalMediumHave application credentials surfaced? See Database Enumeration
3389RDPProvides an interactive Windows desktop sessionConditionalLowAre valid Windows credentials available? See Windows Remote Access
5432PostgreSQLHosts PostgreSQL databasesConditionalMediumHave application credentials surfaced? See Database Enumeration
6379RedisStores key-value data, commonly as an application’s session or cache storeHighHighDoes it answer INFO without a password, and which user does the daemon run as? See Database Enumeration
5985/5986WinRMProvides remote Windows management over HTTP or HTTPSConditionalLowDo known credentials permit a PowerShell session? See Windows Remote Access

How the Services Relate

Windows services often describe a single attack surface rather than independent ports:

  • DNS locates the domain and its controllers.
  • Kerberos authenticates domain identities.
  • LDAP exposes directory objects and relationships.
  • SMB provides shares, named pipes, and remote administration paths.
  • MSRPC exposes management interfaces used by enumeration and remote actions.
  • WinRM and RDP turn valid credentials into remote access when the account is permitted to log on.

On Unix-like targets, rpcbind on 111 commonly points to NFS on 2049 or another dynamically assigned port. Query the mapper before treating each high port as an unrelated service.

Decision Rules

  • Identify the service before choosing commands. A familiar port can host unfamiliar software.
  • Try unauthenticated enumeration once, then park the service if it requires credentials.
  • Revisit SMB, LDAP, WinRM, RDP, SSH, and databases whenever credentials surface. Include HTTP on Windows targets, since IIS features such as WebDAV authenticate against Windows accounts rather than an application login. See WebDAV.
  • Check what a service will accept before spending a credential on it. SSH with PasswordAuthentication no cannot take a password from any user, so a reuse test there returns Permission denied (publickey) regardless of how good the credential is. nmap -p22 --script ssh-auth-methods TARGET settles it in advance and redirects the reuse test to the services that can actually answer it (Sorcerer).
  • Treat UDP as a separate attack surface. DNS, SNMP, Kerberos, and rpcbind may answer over UDP even when the TCP scan is quiet.
  • Record what the service revealed and the next action in the attack-surface table from Information Gathering.