CVE-2024-21182 Google Chronicle · YARA-L

Detect Oracle WebLogic Server CVE-2024-21182 Exploitation Attempt in Google Chronicle

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

Tactic
Initial Access Execution Lateral Movement

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule oracle_weblogic_cve_2024_21182_exploit {
  meta:
    author = "df00tech Detection Engineering"
    description = "Detects exploitation attempts targeting Oracle WebLogic CVE-2024-21182"
    severity = "CRITICAL"
    priority = "HIGH"
    reference = "https://www.oracle.com/security-alerts/cpujul2024.html"
    mitre_attack_tactic = "Initial Access, Execution"
    mitre_attack_technique = "T1190"

  events:
    $http.metadata.event_type = "NETWORK_HTTP"
    $http.target.port in (7001, 7002, 4848, 9002)
    (
      re.regex($http.target.url, `.*/wls-wsat/.*`) or
      re.regex($http.target.url, `.*/_async/.*`) or
      re.regex($http.target.url, `.*/uddiexplorer/.*`) or
      re.regex($http.target.url, `.*/bea_wls_internal/.*`) or
      re.regex($http.target.url, `.*/console/.*`)
    )

  match:
    $http.principal.ip over 15m

  outcome:
    $risk_score = max(95)
    $source_ip = array_distinct($http.principal.ip)
    $target_url = array_distinct($http.target.url)
    $http_method = array_distinct($http.network.http.method)
    $response_code = array_distinct($http.network.http.response_code)

  condition:
    $http
}
critical severity medium confidence

Google Chronicle YARA-L rule for detecting CVE-2024-21182 exploitation attempts against Oracle WebLogic Server. Uses UDM HTTP event telemetry to identify requests to known vulnerable WebLogic endpoints.

Data Sources

Chronicle UDM HTTP eventsWeb proxy logs ingested to ChronicleNetwork detection logs

Required Tables

udm_events

False Positives & Tuning

  • Internal WebLogic cluster communication between managed servers
  • Legitimate SOAP web service calls using WebLogic WS-AT endpoints
  • Authorized security scanning from known vulnerability management IPs
  • WebLogic console access from authorized administrator workstations

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.

  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