Port 1521/tcp: Oracle Database (Oracle Net Listener)
Category: Databases. Range: registered. Status: de facto standard.
What runs here
The conventional default port for the Oracle Net Listener, the process that brokers incoming client connections and hands them off to an Oracle Database instance over Oracle's TNS (Transparent Network Substrate) protocol. Notably, IANA's registry does not actually assign 1521 to Oracle. It's registered to 'ncube-lm' (nCube License Manager); Oracle's own officially IANA-registered ports are 2483/2484 (plain/TLS), but 1521 remains the overwhelmingly dominant real-world default carried forward from decades of Oracle deployment convention.
Why it matters
An exposed listener on 1521 is a reconnaissance goldmine: unauthenticated TNS requests can enumerate configured service names (SIDs) via commands like a TNS PING or version query, and historically weak/default listener configurations (no listener password, or default accounts such as SCOTT/TIGER) have enabled unauthorized database access without ever touching an application. It's a routine pivot point in assessments and real intrusions targeting Oracle-backed ERP/financial systems.
Where you see it
Legitimately: application connection pools, DBA tools (SQL*Plus, SQL Developer), and Oracle Enterprise Manager reaching the listener. Anomalously/maliciously: TNS enumeration/version-fingerprinting probes, SID brute-forcing, or authentication attempts against default Oracle accounts from unexpected hosts.
What to look for
| Signal | What it means |
|---|---|
| TNS listener version probes | Malformed or version-query TNS packets from scanning tools (e.g. tnscmd10g-style probes) indicate reconnaissance against the listener itself, before any database login is attempted. |
| Default account logon attempts | Login attempts using well-known legacy default Oracle accounts (e.g. SCOTT/TIGER, SYSTEM) are a strong sign of an automated or opportunistic attack rather than legitimate application traffic. |
In practice
An externally reachable Oracle listener with no listener password set allows an unauthenticated TNS client to enumerate the instance's registered service names, which the attacker then uses to target a specific SID for credential brute-forcing.