CVE-2024-21182

Oracle WebLogic Server CVE-2024-21182 Exploitation Attempt

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.

Vulnerability Intelligence

KEV — Known Exploited

Affected Software

Vendor
Oracle
Product
WebLogic Server

Timeline

Disclosed
June 1, 2026

CVSS

Unscored
Write-up coming soon

What is CVE-2024-21182 Oracle WebLogic Server CVE-2024-21182 Exploitation Attempt?

Oracle WebLogic Server CVE-2024-21182 Exploitation Attempt (CVE-2024-21182) maps to the Initial Access and Execution and Lateral Movement tactics — the adversary is trying to get into your network in MITRE ATT&CK.

This page provides production-ready detection logic for Oracle WebLogic Server CVE-2024-21182 Exploitation Attempt, covering the data sources and telemetry it touches: CommonSecurityLog, AzureDiagnostics, W3CIISLog, NetworkAccessLog. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Initial Access Execution Lateral Movement
Microsoft Sentinel / Defender
kusto
let weblogic_ports = dynamic([7001, 7002, 4848, 9002]);
let suspicious_paths = dynamic(['/wls-wsat/', '/bea_wls_internal/', '/uddiexplorer/', '/_async/', '/console/']);
union
(
  CommonSecurityLog
  | where TimeGenerated >= ago(24h)
  | where DeviceProduct has_any ("WebLogic", "Oracle")
  | where RequestURL has_any (suspicious_paths)
  | where Activity in~ ("POST", "PUT", "GET")
  | project TimeGenerated, SourceIP, DestinationIP, DestinationPort, RequestURL, Activity, RequestMethod, ResponseCode, DeviceVendor, DeviceProduct
),
(
  AzureDiagnostics
  | where TimeGenerated >= ago(24h)
  | where ResourceType == "APPLICATIONGATEWAYS"
  | where requestUri_s has_any (suspicious_paths)
  | project TimeGenerated, clientIP_s, requestUri_s, httpMethod_s, httpStatus_d, host_s
),
(
  W3CIISLog
  | where TimeGenerated >= ago(24h)
  | where sPort in (weblogic_ports)
  | where csUriStem has_any (suspicious_paths)
  | project TimeGenerated, cIP, csHost, csUriStem, csMethod, scStatus, sPort
)
| extend SuspiciousPath = case(
    RequestURL has "/wls-wsat/", "T3/IIOP deserialization path",
    RequestURL has "/uddiexplorer/", "UDDI SSRF vector",
    RequestURL has "/_async/", "Async deserialization path",
    RequestURL has "/bea_wls_internal/", "Internal WLS endpoint",
    "Unknown suspicious path"
  )
| summarize
    RequestCount = count(),
    UniqueURLs = dcount(RequestURL),
    FirstSeen = min(TimeGenerated),
    LastSeen = max(TimeGenerated),
    Paths = make_set(RequestURL, 20)
    by SourceIP, SuspiciousPath
| where RequestCount > 0
| order by RequestCount desc

Detects HTTP requests targeting known Oracle WebLogic Server vulnerable endpoints associated with CVE-2024-21182 exploitation patterns. Monitors for access to internal WLS paths commonly abused in deserialization and RCE attacks against WebLogic.

critical severity medium confidence

Data Sources

CommonSecurityLog AzureDiagnostics W3CIISLog NetworkAccessLog

Required Tables

CommonSecurityLog AzureDiagnostics W3CIISLog

False Positives

  • Legitimate administrative access to WebLogic console from known admin IPs
  • Internal monitoring or health-check systems polling WebLogic endpoints
  • Vulnerability scanning tools used by internal security teams against WebLogic
  • Load balancer health probes targeting WebLogic listening ports

Sigma rule & cross-platform mapping

The detection logic for Oracle WebLogic Server CVE-2024-21182 Exploitation Attempt (CVE-2024-21182) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: network_connection
  product: windows

Browse the community-maintained Sigma rules for this technique:


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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections