Detect Oracle WebLogic Server CVE-2024-21182 Exploitation Attempt in Splunk
Detects exploitation attempts targeting CVE-2024-21182, an unspecified vulnerability in Oracle WebLogic Server. This CVE is listed in CISA's Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild. Oracle WebLogic Server is a high-value target for threat actors due to its prevalence in enterprise Java EE environments. Exploitation may enable remote code execution, unauthorized data access, or server compromise.
MITRE ATT&CK
SPL Detection Query
index=* (sourcetype=oracle:weblogic OR sourcetype=access_combined OR sourcetype=iis)
(uri_path IN ("/wls-wsat/*", "/bea_wls_internal/*", "/uddiexplorer/*", "/_async/*", "/console/*")
OR dest_port IN (7001, 7002, 4848, 9002))
earliest=-24h latest=now
| eval suspicious_path=case(
like(uri_path, "%/wls-wsat/%"), "T3/IIOP deserialization",
like(uri_path, "%/uddiexplorer/%"), "UDDI SSRF vector",
like(uri_path, "%/_async/%"), "Async deserialization",
like(uri_path, "%/bea_wls_internal/%"), "Internal WLS endpoint",
like(uri_path, "%/console/%"), "Admin console access",
true(), "Unknown"
)
| eval severity=case(
like(uri_path, "%/wls-wsat/%") AND http_method="POST", "critical",
like(uri_path, "%/_async/%") AND http_method="POST", "critical",
like(uri_path, "%/uddiexplorer/%"), "high",
true(), "medium"
)
| stats
count AS request_count,
dc(uri_path) AS unique_paths,
values(uri_path) AS accessed_paths,
values(http_method) AS methods_used,
values(status) AS response_codes,
min(_time) AS first_seen,
max(_time) AS last_seen
BY src_ip, dest_ip, dest_port, suspicious_path, severity
| where request_count > 0
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"),
last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - request_count
| table src_ip, dest_ip, dest_port, suspicious_path, severity, request_count, unique_paths, accessed_paths, methods_used, response_codes, first_seen, last_seenSplunk detection for CVE-2024-21182 exploitation attempts against Oracle WebLogic Server. Monitors web access logs for requests to known vulnerable WebLogic endpoints and correlates with WebLogic application logs.
Data Sources
Required Sourcetypes
False Positives & Tuning
- Legitimate administrative WebLogic console access from authorized admin networks
- Internal application integrations using WebLogic T3 protocol on standard ports
- Security scanner activity from authorized vulnerability management platforms
- Monitoring agents polling WebLogic management endpoints
Other platforms for CVE-2024-21182
Testing Methodology
Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1WebLogic WSAT Endpoint Probe
Expected signal: HTTP GET request logged in WebLogic access.log to /wls-wsat/CoordinatorPortType from attacker IP on port 7001. Network flow data showing connection to WebLogic port.
- Test 2WebLogic Async Servlet POST Probe
Expected signal: HTTP POST to /_async/AsyncResponseService visible in WebLogic access logs and network proxy logs. Process audit logs may show WebLogic JVM processing the request.
- Test 3WebLogic UDDI Explorer SSRF Probe
Expected signal: HTTP GET request to /uddiexplorer/ path logged in WebLogic access log. If SSRF is active, outbound connection attempt from WebLogic server to 127.0.0.1:22 visible in network monitoring.
- Test 4WebLogic Admin Console Access Attempt
Expected signal: HTTP GET to /console/login/LoginForm.jsp in WebLogic access logs. Windows Security event logs may show network logon attempts if authentication is attempted. Network flow logs capture the connection.
Unlock Pro Content
Get the full detection package for CVE-2024-21182 including response playbook, investigation guide, and atomic red team tests.