Skip to content

CVE-2025-30733: Pre-Authentication Memory Leak in Oracle Database Server (RDBMS Listener)

HERMES

HERMES THREAT SCORE & DATABASE EXPOSURE

Target: Oracle Database Server 19c / 21c / 23ai (RDBMS Listener)
Confidence: 94%
68 / 100
MEDIUM

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 14 / 20
Threat Activity 12 / 20
Weaponization 13 / 20
Exposure 15 / 20
Prevalence 16 / 20
Impact 14 / 20
Exploit Maturity 13 / 20
Attack Chain Potential 15 / 20
⚖️ Divergence & Operational Rationale

Hermes assesses CVE-2025-30733 at an HTS of 68 (MEDIUM SEVERITY). While it does not allow direct remote code execution, this pre-authentication network flaw allows attackers to overread memory buffers from the tnslsnr process, leaking cleartext SQL queries, session credentials, and connection metadata.

🕸️ Connected Knowledge Graph & Provenance

CVE-2025-30733: Pre-Authentication Memory Leak in Oracle Database Server (RDBMS Listener)VULNERABILITY

Connected Nodes: 2
Active Relationships (Outgoing)
→ affectsPRODUCTMicrosoft Office & 365 Apps
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

🔍 Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Microsoft Office & 365 Apps documented in Hermes dossier.”

Supporting Verified Evidence:
→ usesATTACK TECHNIQUET1552: Unsecured Credentials
90% VERY_HIGH

Adversaries search compromise victims for unsecured credentials in files, environment variables, or memory.

🔍 Why is this related? (Evidence & Provenance)

“Attack execution telemetry aligns with MITRE ATT&CK technique T1552.”

Supporting Verified Evidence:
ParameterTechnical SpecificationOperational Impact
CVE IdentifierCVE-2025-30733Official NVD / MITRE record
Associated CWECWE-200 / CWE-125: Exposure of Sensitive Information / Out-of-bounds ReadUnauthorized reading of listener process memory
CVSS v3.1 Score6.5 MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
CVSS v4.0 Score6.9 MEDIUMCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Applicable CPEscpe:2.3:a:oracle:database_server:19c:*:*:*:*:*:*:*
cpe:2.3:a:oracle:database_server:21c:*:*:*:*:*:*:*
cpe:2.3:a:oracle:database_server:23ai:*:*:*:*:*:*:*
Enterprise Oracle relational database instances
Affected Versions19.3 through 19.26, 21.3 through 21.17, 23.4 through 23.7Enterprise database listeners exposed on TCP 1521
Fixed Versions19.27, 21.18, 23.8 (Oracle CPU April 2025)Quarterly Critical Patch Update (RU / RUR)

  • CISA KEV: Not listed to date.
  • EPSS Score: 0.00379 (Percentile: 31.3%).
  • Operational Status: Public research PoC demonstrating TNS protocol memory leaks (Driftnet research).
  • PoC & Weaponization: Python TNS packet crafting tools sending malformed CONNECT packets with length mismatches to trigger memory returns.
  • Access Conditions: Pre-authentication; direct network vector (TCP port 1521); low to medium attack complexity.

  • Threat Actors: Reconnaissance groups, Initial Access Brokers (IABs) targeting database tiers.
  • Observed Campaigns: Automated network sweeps scanning for open Oracle Net services.
  • Associated Malware: Custom TNS enumeration modules and offensive memory scrapers.
  • Exploitation Timeline: Documented in Oracle’s April 2025 CPU following coordinated vulnerability disclosure.

  • Anomalous Network Traffic: Bursts of oversized TNS packets with packet length discrepancies directed to port 1521.
  • Target Log Files: listener.log, alert_<ORACLE_SID>.log, trace files in $ORACLE_BASE/diag/tnslsnr/<host>/listener/trace/.
title: Malformed TNS Request to Oracle Listener (CVE-2025-30733)
id: 5a9b7c12-3073-4e89-b123-010203040506
status: test
description: Detects abnormal TNS network packets with size discrepancies targeting Oracle Listener port 1521
references:
- https://www.oracle.com/security-alerts/cpuapr2025.html
- https://driftnet.io/blog/oracle-tns-memory-leak
author: Hermes Codex Research
date: 2026-09-10
logsource:
category: network_traffic
definition: Requires Zeek or Suricata TNS protocol parsing
detection:
selection:
dst_port: 1521
network.protocol: 'tns'
tns.packet_type: 1 # Connect packet
tns.data_length|gt: 2048
condition: selection
falsepositives:
- Complex Oracle OEM management connections with native encryption payloads
level: high
rule Exploit_Oracle_TNS_Leak_CVE_2025_30733 {
meta:
description = "Detects TNS exploit payloads targeting CVE-2025-30733 memory disclosure"
author = "Hermes Codex Research"
date = "2026-09-10"
reference = "CVE-2025-30733"
strings:
$tns_header = { 00 ?? 00 00 01 00 00 00 }
$tns_connect_str = "(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)" ascii nocase
$tns_leak_pattern = { 00 00 08 00 00 00 00 00 ?? ?? FF FF }
condition:
$tns_header at 0 and ($tns_connect_str or $tns_leak_pattern)
}
alert tcp $EXTERNAL_NET any -> $ORACLE_SERVERS 1521 (msg:"HERMES - Oracle Net TNS Malformed Connect Memory Leak (CVE-2025-30733)"; flow:to_server,established; content:"|00|"; depth:1; content:"|01 00 00 00|"; distance:3; within:4; byte_test:2,>,2048,0,relative; classtype:attempted-recon; sid:202530733; rev:1;)
  • Oracle Listener Logs (listener.log): Look for repeated connections failing without * 0 exit codes (TNS-12518, TNS-12502).
  • Process Traces: Check $ORACLE_BASE/diag/tnslsnr/<host>/listener/trace/listener.trc for crash dumps or buffer overruns.
  • MITRE ATT&CK: T1190 (Exploit Public-Facing Application), T1040 (Network Sniffing), T1552 (Unsecured Credentials).

  1. Apply Oracle CPU Patch: Install the April 2025 Release Update (RU): 19.27, 21.18, or 23.8.
  2. Restart TNS Listener: Execute lsnrctl stop followed by lsnrctl start to reload fixed binary libraries.
  3. Enforce Network Segmentation: Restrict TCP port 1521 to trusted application servers via firewall rules and sqlnet.ora directives (tcp.validnode_checking = yes, tcp.invited_nodes = (...)).
  4. Implement Native Network Encryption: Deploy TLS encryption for Oracle Net (TCPS on port 2484) to prevent packet tampering and sniffing.
  5. Rotate Credentials: If the listener was exposed without restriction, rotate all application and database user passwords.

”What happens if this vulnerability is exploited in an enterprise?”

Section titled “”What happens if this vulnerability is exploited in an enterprise?””
  1. Reconnaissance & Listener Discovery: The attacker probes internal segments or DMZs and identifies an unauthenticated Oracle Database Server listener on TCP port 1521.
  2. Triggering the Out-of-Bounds Leak: The adversary sends crafted TNS connection handshakes requesting oversized metadata blocks. The tnslsnr process overreads its internal buffer and echoes uninitialized memory chunks back to the client.
  3. Harvesting Authentication Secrets: By collecting multiple leaked packets, the attacker reconstructs SQL queries, password hashes, and active session tokens belonging to legitimate users.
  4. Legitimate Database Authentication: Armed with recovered credentials, the attacker logs in through standard SQL*Plus or JDBC clients without generating anomalous login failures.
  5. Data Exfiltration & Infrastructure Escalation: The adversary queries confidential corporate tables, exfiltrates intellectual property and customer records, and attempts stored-procedure execution to gain shell access on the underlying database server OS.