Skip to content

Splunk SPL: Oracle WebLogic Integration Broker Request Smuggling Anomaly Hunting — Threat Hunting Query

Density:
Evaluation DimensionObserved Telemetry / AttributeEpistemic Status
Hunting Query IdentifierHUNT-SPLUNK-ORACLE-WEBLOGICCanonical Hunt Node
Target SIEM / Analytics PlatformSplunk Enterprise / CloudTelemetry Ingestion Engine
Platform Syntax Dialectsplunk_splQuery Language Standard
Telemetry & Log SourcesWeb Server Access Logs, WAF Telemetry, F5 BIG-IP / Nginx IngressData Sensor Sources
Targeted Adversary SyndicatesShinyHuntersThreat Attribution
Associated Weaponized CVEsCVE-2026-35273, CVE-2026-96560Vulnerabilities Targeted
Associated Intrusion CampaignsOperation PeopleSoft Infiltration 2026Monitored Campaign
Analytical Confidence98%Hypothesis Validity Score
Primary Evidence SourcesSRC-MANDIANT-GOOGLE, SRC-ORACLE-SECURITYIntelligence Attestation

Adversaries are actively exploiting CVE-2026-35273 to bypass perimeter WAF rules by sending desynchronized HTTP chunks that trigger unauthenticated POST access to internal IntegrationBroker URIs.

Adversary operations frequently slip through standard alerting thresholds by leveraging legitimate binaries or abusing valid service configurations. Proactive threat hunting formulates precise hypotheses based on known architectural chokepoints and queries historical telemetry to unearth stealthy intrusion footholds.


index=web_proxy sourcetype="access_combined" (uri_path="*/IntegrationBroker/*" OR uri_path="*/psc/*")
| eval has_te=if(match(http_headers, "(?i)transfer-encoding"), 1, 0)
| eval has_cl=if(match(http_headers, "(?i)content-length"), 1, 0)
| where has_te=1 AND has_cl=1
| stats count, earliest(_time) as first_seen, latest(_time) as last_seen, values(src_ip) as attacking_ips, values(status) as http_status by uri_path, dest_host
| sort - count

Investigate destination backend hosts receiving status 200/500 with both headers present. Check for subsequent node.js process creations or anomalous outbound HTTPS connections.

  1. Verify Timeline Baseline: Review the first seen and last seen timestamps of returned events to distinguish chronic benign traffic from sudden operational spikes.
  2. Examine Parent-Child Lineage: Ensure that all parent processes match authorized deployment manifests and do not conceal unexpected interactive utilities.
  3. Inspect Network Pivots: Cross-reference communicating source and destination IP addresses against Hermes Adversary Infrastructure endpoints.